101 Reply by TigerC10

(31 replies, posted in Feedback and Support - DriverPacks Base)

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 wink



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.

Go to forum: Feedback and Support - DriverPacks Base

102 Reply by TigerC10

(31 replies, posted in Feedback and Support - DriverPacks Base)

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.

Go to forum: Feedback and Support - DriverPacks Base

103 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

I definetly do. smile

So how should my settings file look if I want to KTD with everything?

Go to forum: Feedback and Support - DriverPacks Base

104 Reply by TigerC10

(31 replies, posted in Feedback and Support - DriverPacks Base)

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



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.

Go to forum: Feedback and Support - DriverPacks Base

105 Reply by TigerC10

(13 replies, posted in Feedback and Support - DriverPacks Base)

Alrighty, I figured out that when I choose to use a custom finisher instead of RunOnceEx or GUIRunOnce the winnt.sif file was being completly overwritten.  When I choose the GUIRunOnce it does add the lines properly.

Go to forum: Feedback and Support - DriverPacks Base

106 Reply by TigerC10

(31 replies, posted in Feedback and Support - DriverPacks Base)

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.

Go to forum: Feedback and Support - DriverPacks Base

107 Reply by TigerC10

(14 replies, posted in Feedback and Support - DriverPacks Base)

Jaak to the rescue! *trumpets blare*

Go to forum: Feedback and Support - DriverPacks Base

108 Reply by TigerC10

(14 replies, posted in Feedback and Support - DriverPacks Base)

Well, if I were you I'd do RVM before the nLite.  Unless you're talking about using the RVM pack in nLite.  If that's the case, then I'd go get RVM's integrator (they do kinda have different ideas about integration) - and run it before you run nLite.

It may not fix your problem, but anything is worth a shot don't you think?



Does the mass storage driver pack have SATA drivers on it?  During windows setup I've always seen it display "press F3 to install 3rd party SATA drivers".  I haven't ever used this option because I have nothing but IDE drives...

Go to forum: Feedback and Support - DriverPacks Base

109 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

The instructions in the ini files say not to set it manually because the base will do it.

Yet my settings ini file wasn't created on my disk.  So I had to make it manually anyway.  And I couldn't find a real clear documention on how to create the settings anyway.  tongue

I understand about the finisher not installing drivers but rather utilities.  It might then be a good idea to have the finisher check and set a registry value to ensure it only gets run once per install.  Or better yet, if the finisher is installing a utility that conflicts with another utility it would be wise to check for the conflicting utility before installing (though, that's FAR more work).

Go to forum: Feedback and Support - DriverPacks Base

110 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

OverFlow wrote:

Since the finisher is wrriten to be pared with the driverpacks and was never intended to be run as a standalone i wouldnt expect any command line function, at all... ever.

I must be confused then...

http://forum.driverpacks.net/viewtopic.php?id=960

How to for making a drivers-only disk?  I mean, I know it wasn't intended to be standalone...  But still...  It would seem that it's progressing to that end.

Go to forum: Feedback and Support - DriverPacks Base

111 Reply by TigerC10

(7 replies, posted in Software)

Yeah, that happens to me sometimes, especially when I download more than one pack at a time.  Just redownload and your problem should be fixed.

Go to forum: Software

112 Reply by TigerC10

(31 replies, posted in Feedback and Support - DriverPacks Base)

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?

Go to forum: Feedback and Support - DriverPacks Base

113 Reply by TigerC10

(4 replies, posted in Hardware)

Well, this is a shot in the dark.  I've much less hardware experience than some of the others around here - but my next course of action (if I had the same issue) would be to uninstall the drivers (software - anything else that came with it), power off and remove the card entirely, and cycle the machine - turn it on and log in only to then turn it off again.  Then reinstall the card and power back up to reinstall the drivers/software.

I've had this work with printers and wireless cards before when something just refuses to work.  It's worth a try. smile  Of course don't ignore jtdoom's questions - that is probably a more productive area of discussion.

Go to forum: Hardware

114 Reply by TigerC10

(1 replies, posted in Feedback and Support - DriverPacks Base)

I believe that KB888111 is the high definition audio update.  If you remove the KB888111.CA_ or KB888111.CAT file from your install disk (I386\svcpack) and delete the "KB888111.CAT" line in your svcpack.inf (you may need to unpack it from svcpack.in_, edit it, and then repack it into the cab) see if you still get the same problem.

Here's a little help with modifying svcpack.inf:
http://www.theeldergeek.com/slipstream_11.htm


EDIT:

2007-07-11 13:47:39 : <SLIP> English (RyanVM's) UpdatePack detected: no HDA hotfix will be slipstreamed.

It shows that you're using RyanVM's update pack, which includes hotfix 888111 - so which pack are you using?  Also - are you using an alternative/mod of RVM pack or the official release?  In whatever case since you're not slipstreaming the HDA hotfix through DriverPacks, try asking around RVM forums and see if there's a reason/fix for why KB888111 presents a flag for lack of windows logo testing.


I did do a search and found the following:

Are you using HFCLEANUP? If you are it's unofficially a known issue.

I had this problem when I used HFCLEANUP instead of nLite to remove Internet Explorer and some other stuff.

If you are, you probably are going to get that message even for drivers that come with Windows XP!

That's a strange issue, if you ask me.

Go to forum: Feedback and Support - DriverPacks Base

115 Reply by TigerC10

(28 replies, posted in News)

YAY!  *votes*

Go to forum: News

116 Reply by TigerC10

(28 replies, posted in News)

I clicked the vote link and didn't get a chance to submit a vote...  It just showed me the results thus far. sad

Go to forum: News

117 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

Figures.  Although, is Bashrat able to reproduce the issue?

Go to forum: Feedback and Support - DriverPacks Base

118 Reply by TigerC10

(13 replies, posted in Feedback and Support - DriverPacks Base)

Yeah I started fresh the first time...  When I lost my setup info I was a little confused - because I checked my unattended.txt and it was left alone.  That's when I figured out the difference between winnt.sif and unattended.txt

Go to forum: Feedback and Support - DriverPacks Base

119 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

I've got nothing...  I don't know what to give for the KTD value to keep them all...

Even still I put "false" in for testing purposes and DPsFnshr.exe still complains of the missing settings file.  I think it may have to do with the work directory - for example the windows installer may be working in the root of the system drive, and then it calls everything from cmdlines.txt explicity.  That is the only way I could see it not being able to find the settings file - maybe because it's looking in the work directory (system drive?) instead of the directory on the CD?

Go to forum: Feedback and Support - DriverPacks Base

120 Reply by TigerC10

(13 replies, posted in Feedback and Support - DriverPacks Base)

Sorry I didn't reply as quickly as normal.  Here's the log:

2007-07-03 12:24:22 : <INIT> DriverPacks BASE 7.05.2 initialized.
2007-07-03 12:24:22 : <INIT> Host environment: WIN_2003 Service Pack 1 on X86 CPU.
2007-07-03 12:24:22 : <INIT> Created temporary working directory.
2007-07-03 12:24:22 : <INIT> Imported proxy settings from Internet Explorer.
2007-07-03 12:24:22 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2007-07-03 12:24:22 : <INIT> 	Detected DriverPack Chipset 7.05.1!
2007-07-03 12:24:22 : <INIT> 	Detected DriverPack Chipset 7.06!
2007-07-03 12:24:22 : <INIT> 	Detected DriverPack CPU 7.04.1!
2007-07-03 12:24:22 : <INIT> 	Detected DriverPack Graphics A 7.06!
2007-07-03 12:24:22 : <INIT> 	Detected DriverPack Graphics B 7.05!
2007-07-03 12:24:22 : <INIT> 	Detected DriverPack Graphics C 7.04!
2007-07-03 12:24:22 : <INIT> 	Detected DriverPack LAN 7.06.2!
2007-07-03 12:24:22 : <INIT> 	Detected DriverPack MassStorage 7.07!
2007-07-03 12:24:22 : <INIT> 	Detected DriverPack Sound A 7.07!
2007-07-03 12:24:22 : <INIT> 	Detected DriverPack Sound B 7.07!
2007-07-03 12:24:22 : <INIT> 	Detected DriverPack WLAN 7.06!
2007-07-03 12:24:22 : <INIT> 	Detected 3rd party DriverPack(s).
2007-07-03 12:24:22 : <INIT> 	Finished scanning.
2007-07-03 12:24:22 : <INIT> Detected settings file "D:\Public\Slipstream\Slipstream x86\Drivers (Driver Packs.net)\DPs_BASE.ini".
2007-07-03 12:24:23 : <INIT> Windows XP Professional -  Retail SP2 detected.
2007-07-03 12:24:23 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2007-07-03 12:24:23 : <INIT> Imported settings from settings file.
2007-07-03 12:24:23 : <GUI>  Initialized GUI.
2007-07-03 12:24:23 : <GUI>  Created a list of all available language files.
2007-07-03 12:24:24 : <GUI>  Set the last used language, English, as the GUI language.
2007-07-03 12:24:29 : <GUI>  Refreshed UpdateChecker with success.
2007-07-03 12:26:41 : <GUI>  Start scanning for DriverPacks for the wnt5_x86-32 platform.
2007-07-03 12:26:41 : <GUI>  	Detected DriverPack Chipset 7.05.1!
2007-07-03 12:26:41 : <GUI>  	Detected DriverPack Chipset 7.06!
2007-07-03 12:26:41 : <GUI>  	Detected DriverPack CPU 7.04.1!
2007-07-03 12:26:41 : <GUI>  	Detected DriverPack Graphics A 7.06!
2007-07-03 12:26:41 : <GUI>  	Detected DriverPack Graphics B 7.05!
2007-07-03 12:26:41 : <GUI>  	Detected DriverPack Graphics C 7.04!
2007-07-03 12:26:41 : <GUI>  	Detected DriverPack LAN 7.06.2!
2007-07-03 12:26:41 : <GUI>  	Detected DriverPack MassStorage 7.07.1!
2007-07-03 12:26:41 : <GUI>  	Detected DriverPack Sound A 7.07!
2007-07-03 12:26:41 : <GUI>  	Detected DriverPack Sound B 7.07!
2007-07-03 12:26:41 : <GUI>  	Detected DriverPack WLAN 7.06!
2007-07-03 12:26:41 : <GUI>  	Detected 3rd party DriverPack(s).
2007-07-03 12:26:41 : <GUI>  	Finished scanning.
2007-07-03 12:26:41 : <GUI>  Refreshed UpdateChecker with success.
2007-07-03 12:27:11 : <GUI>  Saved settings!
2007-07-03 12:27:11 : <GUI>  Closed GUI.
2007-07-03 12:27:11 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m2.
2007-07-03 12:27:14 : <PREP> Removed all attributes from \I386.
2007-07-03 12:27:14 : <PREP> Deleted old DriverPacks.
2007-07-03 12:27:15 : <PREP> Deleted old method 2 related files.
2007-07-03 12:27:17 : <PREP> Cleaned up \I386\svcpack.inf.
2007-07-03 12:27:17 : <PREP> Unslipstreamed KB888111.
2007-07-03 12:27:17 : <PREP> Restored \I386\winnt.sif.
2007-07-03 12:27:17 : <PREP> Restored \I386\txtsetup.sif.
2007-07-03 12:27:17 : <PREP> Restored \I386\dosnet.inf.
2007-07-03 12:27:17 : <PREP> Restored original setup: method 2 was used previously.
2007-07-03 12:27:17 : <PREP> Cleaned up \$OEM$\cmdlines.txt.
2007-07-03 12:27:17 : <SLIP> Created necessary directory structure for method 2.
2007-07-03 12:27:17 : <SLIP> Copied files necessary for method 2.
2007-07-03 12:27:18 : <SLIP> Extracted files necessary for method 2.
2007-07-03 12:27:18 : <SLIP> Deleted old presetup.cmd file from \I386.
2007-07-03 12:27:18 : <SLIP> Created \I386\presetup.cmd file.
2007-07-03 12:27:18 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2007-07-03 12:27:19 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2007-07-03 12:27:46 : <SLIP> Copied DriverPacks to \OEM.
2007-07-03 12:27:48 : <SLIP> Extracted and deleted \I386\svcpack.in_.
2007-07-03 12:27:48 : <SLIP> Updated \I386\svcpack.inf file to support KB888111 and KB921401.
2007-07-03 12:27:50 : <SLIP> Updated \I386\txtsetup.sif file to support KB888111.
2007-07-03 12:27:51 : <SLIP> Updated \I386\dosnet.inf file to support KB888111.
2007-07-03 12:27:52 : <SLIP> Updated \I386\dosnet.inf file to support KB921401.
2007-07-03 12:27:52 : <SLIP> Updated \I386\winnt.sif to support method 2.
2007-07-03 12:27:52 : <SLIP> Updated DPsFnshr.ini to enable KTD for all DriverPacks.
2007-07-03 12:27:52 : <SLIP> Updated DPsFnshr.ini to support the custom KTD cache location you've chosen.
2007-07-03 12:27:52 : <SLIP> Slipstream finished in 41 seconds.
2007-07-03 12:27:54 : <CLNP> Temporary working directory successfully deleted.
2007-07-03 12:27:54 : Program terminated.

I'm running it on Windows 2003 Server, and I am still losing the entire winnt.sif file every time.  Here's my winnt.sif file:

; Created to provide default answers to the Windows Setup prompts
[Data]
    AutoPartition=1
    MsDosInitiated="0"
    UnattendedInstall="Yes"

[Unattended]
    UnattendMode=GUIAttended
    OemPreinstall=Yes
    TargetPath=\WINDOWS

[GuiUnattended]
    EncryptedAdminPassword=NO
    AutoLogon=Yes
    AutoLogonCount=1
    OemSkipWelcome=0
    OEMSkipRegional=1
    TimeZone=35

[UserData]
    ProductID=
    FullName=""
    OrgName=""
    ComputerName=Compy386

[Display]
    BitsPerPel=32
    Xresolution=1024
    YResolution=768
    Vrefresh=70

[RegionalSettings]
    LanguageGroup=13,17,3,2,5,16,4,12,15,7,8,10,11,9,6,14,1

[Branding]
    BrandIEUsingUnattended=Yes

[url]Home_Page=www.google.com

[Proxy]
    Proxy_Enable=0
    Use_Same_Proxy=1

[Identification]
    JoinWorkgroup=WORKGROUP

[Networking]
    InstallDefaultComponents=Yes

I have tried replacing it and not replacing it - and if you remember my thread about the T-13 issue I can't get DriverPacks to install at all (it complains of a missing setup file when I try to run finisher at cmdlines.txt).  However without the driver packs the winnt.sif file works beautifully - and actually it works with the driver packs too up until it freezes on me.

As you can tell, I'm being driven up the wall.

Go to forum: Feedback and Support - DriverPacks Base

121 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

The DPsFnshr.ini file that I put into the same directory as DPsFnshr.exe is all set to blank/default values.

I am manually setting the info now - despite the warnings not to manually set them.  heh - if I want to keep all of the drivers, what should the KTD value be set to?

Go to forum: Feedback and Support - DriverPacks Base

122 Reply by TigerC10

(13 replies, posted in Feedback and Support - DriverPacks Base)

Uh..  No.  My entire winnt.sif file is overwritten (not just the lines that DriverPacks needs).  The changes are crucial, yes.  But they were unnecessary since I already had those values DriverPacks changes in place and correct.

Go to forum: Feedback and Support - DriverPacks Base

123 Topic by TigerC10

(13 replies, posted in Feedback and Support - DriverPacks Base)

Uh, every time I slipstream Driverpacks into my disk my winnt.sif unattended setup file is COMPLETLY changed (it's very irritating to put all of those values back in).  The one that I use is already setup with the same values that DriverPacks wants to have in it.

Is this considered a bug or was Driverpacks intended to do this?

Go to forum: Feedback and Support - DriverPacks Base

124 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

I've got this same problem.  I didn't have DPsFnshr.ini in the same location, though.

When I did put the ini in the same location as DPsFnshr.exe, I still experienced the issue.

I am putting the finisher in $OEM$ on my install disk and I'm using cmdlines.txt to call the finisher in my custom finisher method (as opposed to guirunonce or runonceex).

Go to forum: Feedback and Support - DriverPacks Base

125 Reply by TigerC10

(31 replies, posted in Feedback and Support - DriverPacks Base)

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.

Go to forum: Feedback and Support - DriverPacks Base