intel pro/100 for RIS
intel pro/1000 for RIS
真的是好东西！谢谢！收藏了！
很不错啊
顶起来
有收藏价值
我试验不是很成功
[ Last edited by cjyy on 2005-5-4 at 22:26 ]
Originally posted by cjyy at 2005-5-4 22:16:
我试验不是很成功
[ Last edited by cjyy on 2005-5-4 at 22:26 ]
说说吧,哪里有问题,大家一起探讨一下
我在IBM笔记本、DELL台式机、HP台式机、IBM台式机上全试验过的，应该没问题的
[ Last edited by edreamer on 2005-5-4 at 22:43 ]
拷贝I386及PROGRAM时，分别弹出病毒文件提示及长文件名提示，后关闭防火墙并通过压缩方式拷贝两个文件夹，现在弹出提示："No bootable CD, floppy or hard disk was detected.To install an operating system, insert a bootable CD or floppy and restart the virtual machine by clicking the Reset button."请问楼主是什么原因？难道压缩方式拷贝文件夹不行吗，有什么方式屏蔽长文件名不允许拷贝。启动盘是IBMOEMXP及中文菜单超级工具启动盘。
好帖，顶一下！
Originally posted by whw123456789 at 2005-5-7 18:38:
拷贝I386及PROGRAM时，分别弹出病毒文件提示及长文件名提示，后关闭防火墙并通过压缩方式拷贝两个文件夹，现在弹出提示："No bootable CD, floppy or hard disk was detected.To install an operating syste ...
可不可以讲的清楚些呀
拷贝WINPE的I386到远程安装目录下时提示有一个文件名太长不能拷贝，楼主是否碰到过，不知是什么原因？没办法，我就先把I38整个压缩到一个临时文件夹，然后再解压缩到远程安装目录下，覆盖原目录。如此，小黑启动显示DHCP等都运转正常，但显示没有启动景像。
Originally posted by whw123456789 at 2005-5-7 20:33:
拷贝到WINPE的I386远程安装目录下时提示有一个文件名太长不能拷贝，楼主是否碰到过，不知是什么原因？没办法，我就先把I38整个压缩到一个临时文件夹，然后再解压缩到远程安装目录下，覆盖原目录。如此，小黑启动显 ...
我的正常呀,I386没长文件名,再说长文件名WINDOWS 2003也可以支持的呀
WINPE的I386我用的是CCF启动光盘下的I386
Originally posted by whw123456789 at 2005-5-7 18:38:
拷贝I386及PROGRAM时，分别弹出病毒文件提示及长文件名提示，后关闭防火墙并通过压缩方式拷贝两个文件夹，现在弹出提示："No bootable CD, floppy or hard disk was detected.To install an operating syste ...
虚拟机的BIOS没设置好
虽然有点难,我看不太懂,
但是好象就是前几年的"无盘工作站",对吗??
虚拟机的BIOS要如何设置呀，可我发现启动后DHCP、网卡地址等服务都见到了，再按F12就提示启动镜像不可用或没有。请问，为什么在运行RISETUP时要先用XP的启动安装盘作镜像然后再用CCF启动盘的两个目录覆盖，我试过直接用CCF作镜像，但提示不能作为镜像文件。
好贴啊！我也是用X31，我连启动的U盘都没有，看了版主的文章，好像配置还挺复杂的，只能希望不要重装系统了。
Originally posted by 静静心 at 2005-5-9 17:00:
虽然有点难,我看不太懂,
但是好象就是前几年的"无盘工作站",对吗??
不一样,WINDOWS PE主要是用来系统维护的
启动得到一个error msg：
The operating system image you selected does not contain the necessary drivers for your network adapter
MS的KB说了一堆废话
Originally posted by giyear at 2005-5-18 15:55:
启动得到一个error msg：
The operating system image you selected does not contain the necessary drivers for your network adapter
MS的KB说了一堆废话
ＩＢＭ的笔记本采用ＩＮＴＥＬ ＰＲＯ １００或１０００，采用上面的办法就可以啦，看看你的机器上用的是啥网卡，一般在厂商的网站上会有ＲＩＳ的解决办法的
用的是IBM NETVISTA和T41呀，一个是INTEL100一个是INTEL1000，死活就是不可以，郁闷。
送花，收藏，学习。
感觉有点复杂，得好好研究一下。
还要做虚拟机，唉，要升级电脑了。
[ Last edited by zhaochuan on 2005-5-19 at 16:56 ]
Originally posted by zhaochuan at 2005-5-19 15:53:
送花，收藏，学习。
感觉有点复杂，得好好研究一下。
还要做虚拟机，唉，要升级电脑了。
[ Last edited by zhaochuan on 2005-5-19 at 16:56 ]
其实一点不复杂,仔细看一下就好
E版试过装系统没有?
http://218.17.224.169/forum/viewthread.php?tid=254402&fpage=1
[ Last edited by diomandcold on 2005-6-16 at 11:52 ]
Originally posted by diomandcold at 2005-6-16 11:51:
E版试过装系统没有?
http://218.17.224.169/forum/viewthread.php?tid=254402&fpage=1
[ Last edited by diomandcold on 2005-6-16 at 11:52 ]
没试验过用WINDOWS PE安装系统,
不过PXE安装系统的话只要WINDOWS RIS的功能就可以啦,RIS的含义本来就是远程安装系统
edreamer版的强贴好好学习下：）
BTW，
这两天在捣腾 DOS 下通过Microsoft Network Client 访问其它系统的问题，从IBM网站上down到intel pro /1000 Mobile 网卡for DOS驱动，但在VMware下网卡死活无活驱动，郁闷，
[ Last edited by tanmeng on 2005-6-16 at 17:11 ]
Originally posted by tanmeng at 2005-6-16 17:08:
edreamer版的强贴好好学习下：）
BTW，
这两天在捣腾 DOS 下通过Microsoft Network Client 访问其它系统的问题，从IBM网站上down到intel pro /1000 Mobile 网卡for DOS驱动，但在VMware下网卡死活无活驱动，郁闷 ...
这个简单,到http://www.nu2.nu/bootdisk/network/,
可以下载DOS下网卡的驱动
pcntnd.cab (13KB) AMD PCNet Family Ethernet Adapter NDIS v2.0.1 MAC Driver v3.12 1.0 Mar 26, 2002
Used in VMWare.
thanks
我再试试 ：）
收下了，谢谢
安装系统可参考这个
How to Add Third-Party OEM Network Adapters to RIS Installations
View products that this article applies to.
Article ID : 246184
Last Review : September 22, 2003
Revision : 4.0
This article was previously published under Q246184
On this page
SUMMARY
MORE INFORMATION
APPLIES TO
SUMMARY
Adding a network adapter that requires an OEM driver to a CD-ROM-based Remote Installation Service (RIS) image involves some of the same steps as adding one to a typical unattended installation. However, because the installation method begins by using Pre-boot Execution Environment (PXE) and then switches over to Server Message Block (SMB), the network adapter driver and .inf file must be available during Text-mode Setup. If they are not available, you receive the following error message:
The network server does not support booting Windows 2000. Setup cannot continue. Press any key to exit.
When a PXE client connects to a RIS server and is running Client Installation Wizard (CIW), the network adapter is using Universal Network Device Interface to talk to the RIS server. When the installation portion begins, Windows Setup switches to SMB, the network adapter is detected, and the appropriate driver is loaded. Therefore, the driver must be available.
NOTE: This article applies only to CD-based images (those created through the use of Risetup.exe). For additional information on how to add third-party party network adapters to Riprep images, click the article number below to view the article in the Microsoft Knowledge Base:
254078 How to Add OEM Plug and Play Drivers to Windows Installations
Back to the top
MORE INFORMATION
Check with the hardware manufacturer to see if the supplied network adapter driver is digitally signed. (If the drivers from the manufacturer contain a .cat file, it is likely that they have been properly signed.) Drivers signed by Microsoft have been verified and tested to work with Windows. If your driver has not been signed but you still want to use it, make sure to add the following unattended Setup parameter to the .sif file to be used for this image installation:
DriverSigningPolicy = Ignore
NOTE: The default name of the .sif file is RemoteInstall\Setup\Language\Images\Dir_name\I386\Templates\Ristndrd.sif
NOTE: If the OEM driver is an update of an included Windows 2000 driver (for example, has the same name), the file must be signed or Setup uses the included driver instead. 1. On the RIS server, copy the OEM-supplied .inf and .sys file for the network adapter to the RemoteInstall\Setup\Language\Images\Dir_name\i386 folder. This allows Setup to use the driver during the Text-mode portion of the installation.
2. At the same level as the I386 folder on the RIS image, create a $oem$ folder with the following structure:
\$oem$\$1\Drivers\Nic
3. Copy the OEM-supplied driver files to this folder. Note the folder in which the .inf file looks for its drivers. Some manufacturers place the .inf file in a folder and copy the driver files from a subfolder. If this is the case, create the same folder structure below the one you created in this step.
NOTE: If the RIS image was created with RIPREP, you must perform these steps on both the RIPREP image and the RISETUP image that corresponds to the RIPREP image.
4. Make the following changes to the .sif file to be used for this image installation:
OemPreinstall = yes
OemPnpDriversPath = Drivers\Nic
5. Stop and restart the BINL service on the RIS server. Type the following lines at the command prompt, pressing ENTER after each command:
net stop binlsvc
net start binlsvc
NOTE: Stopping and restarting the BINL service is necessary because BINL needs to read all the new network interface card-related .inf files and create .pnf files in the image. Because this is a time consuming task, it is only done once, which is when the BINL service starts.
When you use this method, you can install PXE clients with the OEM network adapters using RIS. If you have multiple network adapters that require OEM drivers, use the steps above for each adapter. Note that PXE clients that have included network adapter drivers are unaffected by these changes and can use this image for installation.
Back to the top
http://support.microsoft.com/default.aspx?scid=kb;en-us;246184