• Registered: 2006-12-25
  • Posts: 4

Topic: Windows setup loops when installing devices.

Hi,

I have various problems with the new 6.12 versions of the DriverPacks. At first building my Windows Setup Disc in the following order - RVM Update Pack, NLiting and then DriverPacks Base it resulted in a BSOD at restart. This way I had multiple files missing when copying drivers. With drivers integrated with NLite it gave the same result.

The second time I experamented and turned it around - RVM Update Pack, DriverPacks Base and then NLite. Now I still have all kind of files missing but it didn't gave a BSOD anymore. After a while Windows Setup starts to detect all hardware in my system. Just over the middle when it has found the graphics adapter it stays in a loop. Loading from HDD and resetting the monitor over and over.

This kind of behaviour is all new to me. With the old versions before updating to 6.12 DriverPacks it all worked like a charm using the first order mentioned. I have build a lot of Windows Setup Discs all with the same configuration and method. Only renewing the Update Packs and DriverPacks themselves.

I use:

- Windows XP SP2 integrated
- DriverPacks Base 6.10
- DriverPacks 6.12
- NLite 1.3 Beta
- RVM Integrator 1.42
- RVM Update Pack 2.15

Thanks.

  • muiz
  • Vista / 7/8 Driverpacks Team
  • Offline
  • From: Netherlands
  • Registered: 2006-07-01
  • Posts: 1,555

Re: Windows setup loops when installing devices.

Post your HWIDS first

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/VVyo3dzRp1allVk-OCdyukcaj701mcdrrsdDOyX2wK8/perpetual:forever/userbar/admin-1.png
DONATE!
HWID's Tool     Read BEFORE you post
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: Windows setup loops when installing devices.

hi
RVM has a very recent fix in updated release 215a

I've seen Nlite break base slipped sources one too many times.
I won't go try use it as last of the preparing right now. When new releases come out, maybe.
Don't use NLite for packing Bâshrat the Sneaky driverpacks, it cannot handle these packs.

what graphics card is in there?

The answer was 42?
Kind regards, Jaak.
  • Registered: 2006-12-25
  • Posts: 4

Re: Windows setup loops when installing devices.

Hi,

Thanks for responding all. I will try NLite 1.21 again instead of 1.3 Beta. I probably shouldn't have post before testing this. With NLite 1.21 and integrating the older DriverPacks it all worked exept for three files that were missing during setup but that wasn't a problem. When I have verified that my old method with new DriverPacks still breaks the installation I will post again.

I will also write down which driver files are missing. I always like installations that don't halt during setup.

Here is my HWIDS output:


===========
PCI devices
===========


PCI\VEN_1002&DEV_4A50&SUBSYS_003A1043&REV_00\4&354AEA31&0&0008: RADEON X800 XT Platinum Edition
PCI\VEN_1002&DEV_4A70&SUBSYS_003B1043&REV_00\4&354AEA31&0&0108: RADEON X800 XT Platinum Edition Secondary 
PCI\VEN_1106&DEV_0258&SUBSYS_00000000&REV_00\3&267A616A&0&00: VIA Standard Host Bridge
PCI\VEN_1106&DEV_0571&SUBSYS_05711849&REV_06\3&267A616A&0&79: VIA Bus Master IDE Controller
PCI\VEN_1106&DEV_1258&SUBSYS_00000000&REV_00\3&267A616A&0&01: VIA Standard Host Bridge
PCI\VEN_1106&DEV_2258&SUBSYS_00000000&REV_00\3&267A616A&0&02: VIA Standard Host Bridge
PCI\VEN_1106&DEV_3038&SUBSYS_30381849&REV_81\3&267A616A&0&80: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_30381849&REV_81\3&267A616A&0&81: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_30381849&REV_81\3&267A616A&0&82: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_30381849&REV_81\3&267A616A&0&83: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3059&SUBSYS_97611849&REV_60\3&267A616A&0&8D: C-Media AC97 Audio Device
PCI\VEN_1106&DEV_3065&SUBSYS_30651849&REV_78\3&267A616A&0&90: VIA Rhine II Fast Ethernet Adapter
PCI\VEN_1106&DEV_3104&SUBSYS_31041849&REV_86\3&267A616A&0&84: VIA USB Enhanced Host Controller
PCI\VEN_1106&DEV_3149&SUBSYS_31491849&REV_80\3&267A616A&0&78: VIA SATA RAID Controller
PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00\3&267A616A&0&88: VIA Standard PCI to ISA Bridge
PCI\VEN_1106&DEV_3258&SUBSYS_00000000&REV_00\3&267A616A&0&03: VIA Standard Host Bridge
PCI\VEN_1106&DEV_4258&SUBSYS_00000000&REV_00\3&267A616A&0&04: VIA Standard Host Bridge
PCI\VEN_1106&DEV_7258&SUBSYS_00000000&REV_00\3&267A616A&0&07: VIA Standard Host Bridge
PCI\VEN_1106&DEV_B198&SUBSYS_00000000&REV_00\3&267A616A&0&08: VIA CPU to AGP2.0/AGP3.0 Controller
PCI\VEN_1814&DEV_0201&SUBSYS_00321737&REV_01\3&267A616A&0&68: Linksys Wireless-G PCI Adapter
20 matching device(s) found.


===========
USB devices
===========

USB\ROOT_HUB\4&122C2065&0                                   : USB Root Hub
USB\ROOT_HUB\4&24E5D10A&0                                   : USB Root Hub
USB\ROOT_HUB\4&28538922&0                                   : USB Root Hub
USB\ROOT_HUB\4&3B0D39C7&0                                   : USB Root Hub
USB\ROOT_HUB20\4&87115DE&0                                  : USB Root Hub
USB\VID_04B4&PID_6560\5&1BFE1C47&0&2                        : Generic USB Hub
USB\VID_066F&PID_4200\6&1FC5F120&0&2                        : SigmaTel USB-IrDA Dongle
USB\VID_0E8F&PID_0003\6&1FC5F120&0&1                        : USB Human Interface Device
8 matching device(s) found.

  • Registered: 2006-12-25
  • Posts: 4

Re: Windows setup loops when installing devices.

Hi,

I found out that NLite is responsable for the missing system files. Using RVM Integrator before NLite corrupts the Windows Setup Disc causing this and thus resulting eventually in the loop I experienced at the setup devices detection. Not sure why I changed the procedure before but it surely didn't work anymore.

Most likely I updated first so that NLite removed all files including the not needed ones from RVM Update Pack making it a cleaner Setup Disc. It seems that NLite cleaned to much this time.

Now I NLited my disc first, updating with RVM Update Pack and finally adding all drivers with method 2. It all works again without any problems. Only thing that didn't work was the auto creation of the username during setup. This was a known problem with NLite 1.2.1. and is back now with NLite 1.3 Beta.

I will leave you all now trying out my new disc for compatability, stability and performance.

Thanks again.

[SOLVED]

Last edited by Whirlinurd (2006-12-26 16:39:17)

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: Windows setup loops when installing devices.

Hi
thanks

did you download the updated RVM hotfix pack 215a?

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: Windows setup loops when installing devices.

another thanks,

I wondered how come the answerfile I made for somebody did not fill in the user.
I had used Nlite to make it
(because it was for a friend living abroad, different timezone etc, etc, I used Nlite rather than editing a "stock" copy I use for Dutch versions.)

so that was the reason...

The answer was 42?
Kind regards, Jaak.
  • Registered: 2006-12-25
  • Posts: 4

Re: Windows setup loops when installing devices.

Yes jtdoom. I used the RVM Update Pack 2.15a including the DirectX Addon Pack 1.1. The latest Windows XP installation is working perfectly. Now I even removed a lot more critical components and services as I usually do. Making my created .iso file now 417mb. The DPfinisher is the only thing that doesn't work for me. For now I set it to custom and manually run it from my system drive. The first run hangs the program. Then I open the taskmanager and end the process. The second time the DPfinisher runs it will finish and cleans all remaining files leaving only the main executable.

All I can say about the answerfile for NLite is that it works for NLite 1.2.1 and not for 1.3 Beta. Probably just something that creeped into the Beta and should work again when the final is released.