DriverPacks.net Forum - Hangup at T-13

Re: Hangup at T-13

null@example.com (TigerC10) — Sat, 21 Jul 2007 03:03:45 +0000

I downloaded all of the updates from MS through their windows update catalog. I only streamlined the ones that worked, some of them produced errors or didn't make sense - that took about 4 or 5 disks before I could break it down to only the updates that worked (some of the downloaded updates were to things that weren't installed - like .NET or Office).

Anyway, I have confirmed it - CMDLINES.TXT was the issue. Although I don't know why it would randomly cause problems the way it did. Sometimes it worked, sometimes it didn't. Very strange. Anyway - it all works now. I'm going to attempt to streamline the drivers one last time - I know where to come if it doesn't work

EDIT:

*thumbs up* Problem Resolved! DriverPacks successfully installs. I still don't know why it was so random before, but w/e - it works now.

Re: Hangup at T-13

null@example.com (OverFlow) — Sat, 21 Jul 2007 01:04:38 +0000

did you grab all the updates from the MS site or are you just useing nlite to slip the Ryan stuff?

Re: Hangup at T-13

null@example.com (Helmi) — Fri, 20 Jul 2007 21:33:04 +0000

Good ole Notepad does splendid job for me ususally.

Using Notepad 2 or Notepad++ if the file become a bit too big for the MS programme to handle, though...

Just mind the encoding options...

Re: Hangup at T-13

null@example.com (TigerC10) — Fri, 20 Jul 2007 21:03:38 +0000

Okay, so what editor do you all use for CMDLINES.TXT - I suspect that it has to do with my editor putting something else in there that I don't see that breaks my windows installer.

Re: Hangup at T-13

null@example.com (TigerC10) — Thu, 19 Jul 2007 14:49:25 +0000

... Jaak, I've said it twice already but I guess you didn't catch it.

I am not using the RVM packs anymore. I started with it, but then when I had this problem I just went and grabbed all of the updates myself and streamlined them through nLite.

I think it has to do with CMDLINES.TXT, I think if I empty that out it will not have issues. It's worth a shot I think.

Re: Hangup at T-13

null@example.com (Jaak) — Thu, 19 Jul 2007 09:01:01 +0000

@ TigerC,
the dutch pack for RVM had a bug in june.. it is apparently fixed, and I have used it without hiccups.

I cannot reproduce what you report.

Re: Hangup at T-13

null@example.com (TigerC10) — Wed, 18 Jul 2007 22:43:01 +0000

Well, I don't think it's DriverPacks anymore...

After having had it out of my disk for some time now, I began having "freeze" issues at T-12 again. It seems to be rather random, sometimes it doesn't freeze, other times it does. It's all rather confusing. I think it's cmdlines.txt, so I'm just going to empty it and stick everything in guirunonce in my winnt.sif file.

But thanks anyways everyone!

BÃ¢shrat the Sneaky wrote:

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?

I signed up for an account, but every time I try to log in to report it, it tells me that I am not allowed or something.

Re: Hangup at T-13

null@example.com (TigerC10) — Sat, 14 Jul 2007 18:51:23 +0000

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?

Re: Hangup at T-13

null@example.com (Wim Leers) — Tue, 03 Jul 2007 22:38:51 +0000

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?

Re: Hangup at T-13

null@example.com (TigerC10) — Tue, 03 Jul 2007 14:13:34 +0000

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.

Re: Hangup at T-13

null@example.com (TigerC10) — Mon, 02 Jul 2007 22:12:53 +0000

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?

Re: Hangup at T-13

null@example.com (mr_smartepants) — Mon, 02 Jul 2007 19:26:13 +0000

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.

Re: Hangup at T-13

null@example.com (Helmi) — Mon, 02 Jul 2007 15:56:32 +0000

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 ):

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 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).

Re: Hangup at T-13

null@example.com (TigerC10) — Mon, 02 Jul 2007 13:06:18 +0000

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

Anyone else know anything that might could help me out?

Re: Hangup at T-13

null@example.com (TigerC10) — Sun, 01 Jul 2007 23:30:45 +0000

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...