RE: English and localized XP versions behave differently with RIS?

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi Michael
Thank you for your reply. It IS the instructions that you post, I have tried.
During my attempts to make it work, I came across numerous BSOD's, mostly
following an attempt to edit the inf-files. Your problems may also be caused
by incompatible inf-files, but in your case the crash may happen before the
OS is able to BSOD.
Essentially we're at the same point in the process, and getting nowhere :-(.
A quick search uncovered this driverpackage especially compiled for RIS.

http://www.doitrightconsulting.net/forum/viewtopic.php?t=315#p1908

Have you tried it? If you do, let me know the results. I don't have one of
the culprit computers at hand at the moment, so I can't do it myself.

Regards
Terje


"Michael C" wrote:

Hi
I am using danish xp and it does not complaine when using this.
but i have problems with the storage, i dont resive any errors but it halt
on black screen.?????

Microsoft Windows XP and Microsoft* Windows Server* 2003 (32-bit)
==================================================================

1. Create an [IMAGE_ROOT]\$oem$\$1\Drivers\NIC directory if one does not
already exist.

2. Copy all files from the PRO1000\Win32 directory to the
[IMAGE_ROOT]\$oem$\$1\Drivers\NIC directory.

3. Make the following changes to the .SIF file that is used for this image
installation (located in the [IMAGE_ROOT]\I386\Templates directory):

[Unattended]
OemPreinstall = yes
OemPnpDriversPath = \Drivers\Nic

4. Copy all .SYS files from PRO1000\Win32 directory to the [IMAGE_ROOT]\i386
directory. Do NOT copy the INF files to this directory.

5. Delete E1000325.PNF, E1E5132.PNF and E1Q5132.PNF (if present) from the
[IMAGE_ROOT]\i386 directory.

6. Extract the .INF files from PRO1000\Win32\RIS_INF\E1000325.ZIP,
E1E5132.zip and E1Q5132.ZIP to the [IMAGE_ROOT]\i386 directory.

7. Restart the Remote Installation Service.

8. Follow the rest of the Microsoft instructions for adding a new network
driver to the RIS installation.
-----------------------------------------------------------------



"Terje Snitker" wrote:

I am in the process of setting up RIS (i. e. legacy mode WDS) to install
Windows XP on a HP Compaq 8510p. When I follow the special directions
(provided with the drivers) for using the network driver with RIS, the
english version of XP installs flawlessly.
But when I switch to the danish version, the setup halts, saying
(translated) that the image does not hold the nescessary drivers for the
networkadapter.
This RIS works fine with numerous other client computers
Has anyone had this type of problem?
What can be done about it?

.

Relevant Pages

  • Re: Shared Epson Printer Wont Print
    ... > The best thing you can do is follow their instructions, ... > "Once you have installed the driver directly from the cd on each client ... >> Even with the print server, some of the features of the AIO may not be available to the network, particularly the scanning feature. ...
    (microsoft.public.windowsxp.network_web)
  • RE: English and localized XP versions behave differently with RIS?
    ... I am using danish xp and it does not complaine when using this. ... Follow the rest of the Microsoft instructions for adding a new network ... driver to the RIS installation. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Buffalo/Broadcom wireless N card
    ... using instructions off a FBSD help page I can't locate just now. ... (I'm working on building a network bridge.) ... is to use the Windows XP driver and FBSD's 'ndis'. ...
    (freebsd-questions)
  • Re: Linux Firewall/LoadBalancer
    ... The bonding driver originally came from Donald Becker's beowulf patches for ... Build kernel with the bonding driver ... "Bonding driver support" in the "Network device support" section. ... so the bonding driver will automatically load when the bond0 interface is ...
    (Security-Basics)
  • [SPARC] Problem with "Happy Meal" drivers
    ... I also use two network cards handled by your driver: ... # Loadable module support ... Unimplemented SPARC system call 188 ...
    (Linux-Kernel)