• Registered: 2007-06-29
  • Posts: 140

Topic: Hangup at T-13

I have a large network to manage, and with all sorts of machines (Dells and Gateways and HPs - oh my!) I found that the goal of this community is a network admin's best friend.

However, after using the driverpacks base with all of the driver packs (call me crazy, but I also went and got all of the 3rd party driver packs just in case) it seems to make my windows XP install hang at T-13.  I was actually quite reluctant to believe that it was DriverPacks doing this to my installer, but after testing everything else, the only thing that causes the "freeze" is Driver Packs.

I was REALLY looking forward to it working, and I didn't know where else to turn.  The windows installer just continues cycling through the little built-in ads, but never advances the progress bar about halfway through the T13.

I am using a Corperate Volume Edition for Windows XP Pro, SP2.  I have streamlined all of the updates that I can with exception of one that has reported to cause problems.  All that's left is to add in driverpacks, and it's always the last thing I do before creating an install disk.



I was only able to get the install to work under one test case - and in that test case I had accidentally slipstreamed an alternate language update into the disk.  After taking out that issue it went right back to hanging up at T13.

EDIT:
I did search the forums, but I couldn't find anything similar to my issue.


Thanks in advance!

Last edited by TigerC10 (2007-06-29 15:41:09)

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

Re: Hangup at T-13

hi
do you still have Graphics A 7.04 or 7.05.2?
I ask, because this was stable.

And yesterday a Mass storage controller issue was reported, and it was caused by an LSI update done about fourteen days ago, which happened to have support for DELL.
The Mass storage DriverPacks update is ready for upload.

The answer was 42?
Kind regards, Jaak.
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

I've been attempting with the latest stuff for the last 5-6 days.  Every time I use the DPBase I look for updates - anything that's outdated I update.  Currently the Graphics A that I have is 7.06, but I think the issues I was having was with the one right before that one (7.05.2, maybe?)
.  I downloaded 7.06, but haven't tested it yet (was working on some other issues with the install disk).  I'll try the new packs and post my conclusions.

My test installs were on a Gateway, would that affect the Mass Storage driver pack?

EDIT:
Thanks for the quick reply, btw.  Fantastic! *thumbs up* smile

Last edited by TigerC10 (2007-06-29 15:47:20)

~TigerC10~
  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: Hangup at T-13

T-13 is the SVCPACK stage of install.  AFAIK, the only items installed during this stage are contained in the %cdrom%\i386\svcpack\ folder...nothing else (unless you have a .cmd file in there pointing somewhere else.)
Can you post the contents of your svcpack.inf file? (it's a CAB compressed file normally named svcpack.in_ and it's located in the i386 directory.)

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

Right, I know that it is the svcpack and cmdlines.txt parse.  I only things I might have in there are the windows updates and one RyanVM addon for .NET 1.1 - that's why I was so reluctant to believe that it was Driverpacks.  Without Driverpacks, everything worked fine.  When I added it in - it would hangup.  Go figure.

The text above the progress bar was, "Registering Components" and the progress bar would get up to the letter "p" and hang.

~TigerC10~
  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: Hangup at T-13

When you get the hang, does the .NET 1.1 installer finished?  Or has it even begun?
I use RyanVM's update pack v2.1.11 and .NET AIO (.NET 1.1, 3, runtimes) switchless installer at T-13 and everything is perfect.

Post your svcpack.inf text please. smile

Last edited by mr_smartepants (2007-06-30 00:59:53)

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

Very well, here it is smile

[Version]
Signature="$WINDOWS NT$"
MajorVersion=5
MinorVersion=1
BuildNumber=2600

[SetupData]
CatalogSubDir="\I386\svcpack"

[ProductCatalogsToInstall]
BASECSP.CAT
IDNDL.CAT
IE7-KB928090.CAT
IE7-KB929969.CAT
IE7-KB933566.CAT
IE7.CAT
KB873339.CAT
KB885250.CAT
KB885523.CAT
KB885626.CAT
KB885835.CAT
KB885836.CAT
KB886185.CAT
KB887472.CAT
KB887742.CAT
KB887797.CAT
KB888113.CAT
KB888302.CAT
KB888316.CAT
KB890046.CAT
KB890859.CAT
KB891781.CAT
KB893066.CAT
KB893756.CAT
KB893803V2_NET.CAT
KB893803V2_WXP.CAT
KB894391.CAT
KB895953.CAT
KB896344.CAT
KB896358.CAT
KB896422.CAT
KB896423.CAT
KB896424.CAT
KB896428.CAT
KB896688.CAT
KB898461.CAT
KB898543.CAT
KB899587.CAT
KB899588.CAT
KB899589.CAT
KB899591.CAT
KB900485.CAT
KB900725.CAT
KB900930.CAT
KB901017.CAT
KB901190.CAT
KB901214.CAT
KB902400.CAT
KB904706.CAT
KB904942.CAT
KB905414.CAT
KB905749.CAT
KB905915.CAT
KB908519.CAT
KB908531.CAT
KB910437.CAT
KB911280.CAT
KB911562.CAT
KB911567.CAT
KB911927.CAT
KB912024.CAT
KB912812.CAT
KB912919.CAT
KB913446.CAT
KB913580.CAT
KB913808.CAT
KB914388.CAT
KB914389.CAT
KB915865.CAT
KB916281.CAT
KB916595.CAT
KB917159.CAT
KB917344.CAT
KB917422.CAT
KB917537.CAT
KB917953.CAT
KB918118.CAT
KB918439.CAT
KB918899.CAT
KB919007.CAT
KB920142.CAT
KB920213.CAT
KB920214.CAT
KB920342.CAT
KB920670.CAT
KB920683.CAT
KB920685.CAT
KB920872.CAT
KB921398.CAT
KB921883.CAT
KB922582.CAT
KB922616.CAT
KB922760.CAT
KB922819.CAT
KB923191.CAT
KB923414.CAT
KB923689.CAT
KB923694.CAT
KB923980.CAT
KB924191.CAT
KB924270.CAT
KB924496.CAT
KB924667.CAT
KB925454.CAT
KB925486.CAT
KB925720.CAT
KB925902.CAT
KB926247.CAT
KB926255.CAT
KB926436.CAT
KB927779.CAT
KB927802.CAT
KB927891.CAT
KB928090.CAT
KB928255.CAT
KB928388.CAT
KB928843.CAT
KB929123.CAT
KB929338.CAT
KB929969.CAT
KB930178.CAT
KB930916.CAT
KB931261.CAT
KB931768.CAT
KB931784.CAT
KB931836.CAT
KB932168.CAT
KB933566.CAT
KB935448.CAT
KB935839.CAT
KB935840.CAT
LIPSP2QFE.CAT
NLSDL.CAT
MC05Upd1.cat
KB914548.cat
KB919803.cat
KB925766.cat

[SetupHotfixesToRun]
kb888316.exe /q /n /z /o
KB927978.EXE /quiet
KB927977.EXE /quiet
lipsp2qfe.exe /q /n /z /o
kb895953.exe /q /n /z /o
kb913808.exe /q /n /z /o /b:sp2gdr
kb920142.exe /q /n /z /o /b:sp2qfe
kb923689.exe /q /n /z /o
kb928388.exe /q /n /z /o /b:sp2gdr
kb931836.exe /q /n /z /o /b:sp2gdr
mc05upd1.exe /q /n /z /o
kb914548.exe /q /n /z /o
kb919803.exe /q /n /z /o
kb925766.exe /q /n /z /o

[CatalogHeader]

; Customized by nLite - www.nliteos.com

As you can tell, it was created and packed with nLite.  This is BEFORE any driverpacks get included.


As for after the driverpacks get included.  Here:

[Version]
Signature="$Windows NT$"
MajorVersion=5
MinorVersion=1
BuildNumber=2600

[SetupData]
CatalogSubDir="\I386\SVCPACK\"

[ProductCatalogsToInstall]
KB921401.CAT
KB888111.CAT
BASECSP.CAT
IDNDL.CAT
IE7-KB928090.CAT
IE7-KB929969.CAT
IE7-KB933566.CAT
IE7.CAT
KB873339.CAT
KB885250.CAT
KB885523.CAT
KB885626.CAT
KB885835.CAT
KB885836.CAT
KB886185.CAT
KB887472.CAT
KB887742.CAT
KB887797.CAT
KB888113.CAT
KB888302.CAT
KB888316.CAT
KB890046.CAT
KB890859.CAT
KB891781.CAT
KB893066.CAT
KB893756.CAT
KB893803V2_NET.CAT
KB893803V2_WXP.CAT
KB894391.CAT
KB895953.CAT
KB896344.CAT
KB896358.CAT
KB896422.CAT
KB896423.CAT
KB896424.CAT
KB896428.CAT
KB896688.CAT
KB898461.CAT
KB898543.CAT
KB899587.CAT
KB899588.CAT
KB899589.CAT
KB899591.CAT
KB900485.CAT
KB900725.CAT
KB900930.CAT
KB901017.CAT
KB901190.CAT
KB901214.CAT
KB902400.CAT
KB904706.CAT
KB904942.CAT
KB905414.CAT
KB905749.CAT
KB905915.CAT
KB908519.CAT
KB908531.CAT
KB910437.CAT
KB911280.CAT
KB911562.CAT
KB911567.CAT
KB911927.CAT
KB912024.CAT
KB912812.CAT
KB912919.CAT
KB913446.CAT
KB913580.CAT
KB913808.CAT
KB914388.CAT
KB914389.CAT
KB915865.CAT
KB916281.CAT
KB916595.CAT
KB917159.CAT
KB917344.CAT
KB917422.CAT
KB917537.CAT
KB917953.CAT
KB918118.CAT
KB918439.CAT
KB918899.CAT
KB919007.CAT
KB920142.CAT
KB920213.CAT
KB920214.CAT
KB920342.CAT
KB920670.CAT
KB920683.CAT
KB920685.CAT
KB920872.CAT
KB921398.CAT
KB921883.CAT
KB922582.CAT
KB922616.CAT
KB922760.CAT
KB922819.CAT
KB923191.CAT
KB923414.CAT
KB923689.CAT
KB923694.CAT
KB923980.CAT
KB924191.CAT
KB924270.CAT
KB924496.CAT
KB924667.CAT
KB925454.CAT
KB925486.CAT
KB925720.CAT
KB925902.CAT
KB926247.CAT
KB926255.CAT
KB926436.CAT
KB927779.CAT
KB927802.CAT
KB927891.CAT
KB928090.CAT
KB928255.CAT
KB928388.CAT
KB928843.CAT
KB929123.CAT
KB929338.CAT
KB929969.CAT
KB930178.CAT
KB930916.CAT
KB931261.CAT
KB931768.CAT
KB931784.CAT
KB931836.CAT
KB932168.CAT
KB933566.CAT
KB935448.CAT
KB935839.CAT
KB935840.CAT
LIPSP2QFE.CAT
NLSDL.CAT
MC05Upd1.cat
KB914548.cat
KB919803.cat
KB925766.cat

[SetupHotfixesToRun]
kb888316.exe /q /n /z /o
KB927978.EXE /quiet
KB927977.EXE /quiet
lipsp2qfe.exe /q /n /z /o
kb895953.exe /q /n /z /o
kb913808.exe /q /n /z /o /b:sp2gdr
kb920142.exe /q /n /z /o /b:sp2qfe
kb923689.exe /q /n /z /o
kb928388.exe /q /n /z /o /b:sp2gdr
kb931836.exe /q /n /z /o /b:sp2gdr
mc05upd1.exe /q /n /z /o
kb914548.exe /q /n /z /o
kb919803.exe /q /n /z /o
kb925766.exe /q /n /z /o

[CatalogHeader]

; Customized by nLite - www.nliteos.com

Looks the same to me?  Does Driverpacks alter the svcpack?

EDIT:
Yeah, I used RyanVM pack v2.1.10 and it hung up so I tooked it out and just slipstreamed everything with nLite (took forever to get my hotfix library up to date, not to mention taking out the ones that can't/shouldn't be slipstreamed).  I also forgot to mention that I slipstream WMP11 with that special slipstreamer (with its updates) and I use NR's IE7 addon.

But that's it.

As far as knowing if it installed or not - I couldn't say.  I let it run for a day and a half and it didn't budge...  When I rebooted, I ended up starting the whole process over again.  How might I be able to tell?

Last edited by TigerC10 (2007-06-30 02:26:44)

~TigerC10~
  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: Hangup at T-13

The only difference I could find is after DP integrated, these are added:

[ProductCatalogsToInstall]
KB921401.CAT
KB888111.CAT

It's been discussed twice here:
http://forum.driverpacks.net/viewtopic.php?id=299
http://forum.driverpacks.net/viewtopic.php?id=828

Why they're being integrated by DPBase, I don't know.  Maybe Bâshrat the Sneaky can shed some light on the subject.
I know for a fact that DPBase will NOT install KB888111 if it detects RyanVM update pack was installed, not sure about the other.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

Hmmm, well I just gave it a shot with the most up-to-date packs and I got to T-12 before the hangup.  Although, it was pretty much the same percentage on the progress bar - so I think that I'm getting stuck right at the T-13 and T-12 points.

Regardless, those are official MS Patches, right?  Why would they break the install process?  I don't see anything about them causing problems with the install process, and I did a quick google search and didn't see anything.

I would imagine that these are none essential, so I'll try taking them out and see what happens.

~TigerC10~
  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: Hangup at T-13

Well, I know that KB888111 is needed to detect High Definition Audio devices correctly.  So if you don't have HDAudio, take it out.  The other KB item is to fix MIDI audio (which nobody uses anymore).  smile

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

Nope.  I took out those two updates and it didn't work.

I double checked and manually added them - but didn't do driver packs and I got through the installation and it worked.  I'm a little weirded out.


EDIT:
Using disc platform, Method 2 with KTD (all) and disabled QSC.  Slipstreaming everything except I'm not doing mass storage text mode.  I have a custom finisher, but that shouldn't matter.  Only thing is that when I click on "overview" it tells me I'm using GUIRunOnce even though I chose to do custom.  Could that be the issue?

Last edited by TigerC10 (2007-07-02 06:46:33)

~TigerC10~
  • Helmi
  • Moderator & Translator (German)
  • Offline
  • From: Germany
  • Registered: 2006-05-27
  • Posts: 1,799

Re: Hangup at T-13

Just a shot in the dark, but...

Maybe try enabling QSC for a chance.
In the past, some users had problems with it disabled for w/e reason and it worked when they used it...

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/AeXmpESLemRyQ4RE-dgdjRhN_hKaXMe7woWjOK2wsnk/perpetual:forever/userbar/moderator-3.png

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

I can give it a try, I disabled it because it said that it was recommended to do so with method 2.


EDIT:
Uhhh, well - I decided to double check and make sure that the .cat files were added by the base when they were added into the inf.  I can't find KB888111 in the svcpack folder.  I did find the other one though, and it was compressed already which was nice.

Perhaps this might be the REAL issue at hand.


EDIT 2:
AH HA!  When I chose to enable QSC the KB888111.ca_ file appeared in the svcpack directory.  big_smile

Last edited by TigerC10 (2007-07-02 08:12:03)

~TigerC10~
  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: Hangup at T-13

Pure magic! smile

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

So uh.... What...  Should this be elevated to a bug in the DP Base?  Can anyone reproduce the issue or is it just me?

EDIT:
It occurred to me that even when I took the lines out of the svcpack inf, I still had the issue.  Perhaps this is not the "pure magic" I was hoping for.  I still need to try now that I've enabled QSC - I'll report back with the news.

Last edited by TigerC10 (2007-07-02 08:37:07)

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

Re: Hangup at T-13

Hi
was this with method 1?

The answer was 42?
Kind regards, Jaak.
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

The hangup happened with method 2 and QSC disabled.  I'm currently trying method 2 with QSC enabled.  When I used method 2 and QSC disabled the KB888111.ca_ was NOT placed in the svcpack directory - and it was added to the svcpack.inf.

The KB888111.ca_ did get placed in the SVCPACK folder when I chose to enable QSC.

~TigerC10~
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

Okay, so...  I just verified that I still experience the hangup at T-12 now with QSC enabled.

Here are my settings, maybe I'm doing something wrong.


Installation Platform:
disc

All Driverpacks (including 3rd party - NO mass storage text mode)
Method 2
Custom Finisher

Keep The Drivers Enabled for ALL driver packs
Custom cache location - %SystemRoot%\system32\DeviceDrivers
QSC Enabled
ATI Catalyst Control Panel (not Control Center)

-------------------------------------------------------------------------------

All driver packs are up-to-date
I've tried with QSC disabled, but that didn't add the KB888111 cat file when it added it to the svcpack.inf
I still see "finisher method" listed as GUIRunOnce when I look at overview.


I am really close to giving up on driver packs...

~TigerC10~
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

Uh...  I said really close - not that I am yet.

Anyone else know anything that might could help me out?

Last edited by TigerC10 (2007-07-03 00:36:31)

~TigerC10~
  • Helmi
  • Moderator & Translator (German)
  • Offline
  • From: Germany
  • Registered: 2006-05-27
  • Posts: 1,799

Re: Hangup at T-13

TigerC10 wrote:

Anyone else know anything that might could help me out?

Well, call it pure magic or whatever, but I just happened to stumble across this yesterday (and immediately had to think of your problem, too wink):

http://www.ryanvm.net/forum/viewtopic.php?t=4068

Actually, I'm planning on using this myself the next time I come across a HDA system because I had problems with that in the past.

As you are in fact using the RVM Update Pack (I would have posted this regardless), I would definately give this a try - apparently it is a well-known problem (i.e. not isolated to you); and this would also mean it's probabaly really not us to blame but rather Ryan (not to diss his otherwise outstanding work, heh wink Probabaly MS to blame anyway).

HTH and hoping for you to report back (seeing as I cannot test this myself current for the lack of any affected systems).

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/AeXmpESLemRyQ4RE-dgdjRhN_hKaXMe7woWjOK2wsnk/perpetual:forever/userbar/moderator-3.png

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!
  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: Hangup at T-13

The other thing to consider is that Ryan's update pack was designed to work with the RVMIntegrator.  Nlite works around this by it's own method.  I'm not sure of the details, but it usually sparks off a flamewar of which method is better.
In almost every case around here where people have problems with kb888111, nlite is used in conjunction with the RyanVM update pack.
Might be a coincidence...or it might not.

Anyway, try integrating from a virgin source using the RVMIntegrator (updatepack/addons to start), then use nlite(removals/tweaks), then driverpacks.  It's my method and works rather well.

Last edited by mr_smartepants (2007-07-03 06:58:35)

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

Um... Sorry to mislead you two with ambiguity.  I originally used RVM's pack, but when I had this T-13/T-12 problem I took it out and opted for streamlining each patch individually through nLite (I too thought it was RVM).  Since I have only been able to produce this issue after doing driver packs, I can only be lead to believe it is Driver Packs...

I decided to take my custom finisher and move it from executing in a .cmd to executing at cmdlines.txt - I FINALLY GOT AN ERROR this way.

The DPFinisher popped up and said, "couldn't locate settings file" or something like that.  Then I experienced the exact same hangup.  What settings file might it be talking about?

~TigerC10~
  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

Couldn't find a post before, but then I saw this one today - http://forum.driverpacks.net/viewtopic.php?id=1704

Workin' on resolving my issue again.

~TigerC10~
  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: Hangup at T-13

I've quickly read through this thread and I can assure you that both hotfixes are valid hotfixes and have worked fine for a long time.
You seem to have found a bug though - please report it in the bug tracker so I won't forget to fix it.

Have you narrowed it down any further already?

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • Registered: 2007-06-29
  • Posts: 140

Re: Hangup at T-13

I've finally found something about Windows setup stalling at T-12

http://www.msfn.org/board/index.php?showtopic=15606

It stalls for this person because of an asterisk instead of a "" in a cmd file (which prompts a user - and the cmd window being hidden then pauses the install indefinetly), and I haven't done anything like that.  I suppose DriverPacks doesn't do this either?

Last edited by TigerC10 (2007-07-15 06:26:53)

~TigerC10~