Search options (Page 3 of 6)

I thought you were doing a NIS.  If that's the case then your SVCPACK.inf wouldn't need a new CD every time because the CD just tells the installer to look on the network for the installation stuff.  I think I read that someone was going to integrate the CPU and Chipset drivers to their boot NIS CD, and then integrate all of the other packs to the NIS Location.

I don't think this'll solve your problem, but some things you may want to consider:

1.) Enable QSC (it avoids a bug where some .CAT files are not properly copied into the svcpack directory despite having their entries added into the svcpack.inf).

2.) Make sure you've got .NET in your installation (because of the ATI thing; RVM has a nice switchless .NET 1.1 SP1 installer that can be added to your svcpack.inf)

Did you attempt doing a disc install before trying NIS?  If you can't get a disc to install then there's something going wrong either before/during DriverPacks.  If you can, then there's something wrong with the way you're doing NIS.

To quote one of the most beloved characters in all of cartoon history:
"YAY I'M DOOMED!"

haha, maybe.

Well, I could hang a DVD on the system - but I don't have any spares.

I slipstreamed all of the DriverPacks as well as the 3rd parties.  They don't fit on a CD.  I could remove the 3rd parties - how could I just take out the 3rd parties.

Yeah, that's what I meant.  Sorry about the typo...

Well, instead of doing a NIS try doing a single disc installation.  If the disc installation works then it is a problem with how you're doing your NIS.  If the disc fails, then it's a problem with however you're doing things to the disc (including the possibility of DriverPacks).

filename_on_source=diskid,subdir,upgradecode,newinstallcode,spare,spare,newfilename

Do you notice that the only 2 files you have a problem with are the only two files with "2,0,0" at the end?  That's actually the default value, but since you're doing a NIS you may need to alter that...  Not sure.  I've never done NIS.

The other thing you may need to consider is a file corruption when you copy it.  It's happened to me before.

Wait, you're doing a NIS?  Not a disc install?

Okay, well - first thing you should know is that DriverPacks will alter your winnt.sif file - which is used for disc installations.  Since you're doing a Network Install Setup you need to add those additional/modified entries to your UNATTEND.TXT file (from what I understand, the only difference between these files should be the name).

Finally, since you said the setup.ex_ is not there anymore - just manually copy it back over.  Also copy presetup.cmd since you had problems with that one too.  If you want, try looking here:
http://unattended.msfn.org/unattended.xp/view/web/35/

They have the files available for download if you don't want to re-copy them from the disc.

Yeah.  The base says that.  When I had my problem a few months ago I found that because I wasn't enabling the QSC it wasn't adding the .CAT files to the svcpack - but it did alter the svcpack inf to include the lines for the corresponding updates.  When I tried to use the bug tracker to report the issue my account never would activate...  Never could log in. lol Anyway I was afraid to enable QSC because the base said it was recommended not to.  It's not a big deal though.

Anyway, despite being told to use QSC for method one, you should enable for method 2 anyway so that you don't have that issue.

You're all over the place with your tools...

You shouldn't need to use nLite to rip the source disk.  Just copy all of the files from the CD to a place on your hard drive.  It's easier that way.

Then you should create your winnt.sif file (just in case RVM uses it, but it probably doesn't).

Then you can use RVM to update everything.

Then you should integrate the DriverPacks (driverpacks does alter your winnt.sif file, so creating it after the DriverPacks integration will get rid of the alterations needed).

Finally you should create a bootable data disk ISO with Nero, instead of using RVM or nLite (they can mess stuff up).  CDGUI is good too.  After that burning it shouldn't be a problem.

EDIT:
Your winnt.sif file seems to still have the data altered by DriverPacks, so I think that it's just that you're using a different tool for making your iso.