GreenMachine

Yes, PhillTheChill, SVC-EXE should work fine, and will be run at the end of SVCPACK.INF, at T-13.

There is a known bug with the BOOTIMGFILE value in XPCREATE.INI that causes this. It'll be fixed next release. I found it was not enough of a show stopper to make a special release.

Sorry ... but I have to repeat myself here. If your ISO is so big, you are obviously installing other applications and whatnot. I don't believe that the drivers themselves add so much. So ... First make a FailSafe CD, using only the hotfixes listed onthe Web Site/Current Hotfixes. Once that is working, go from there, step at a time, and you will find out what is causing your problems. For future reference ... please include your files in either CODE Blocks, or, better yet, as attachments. For general information, the only file I tend to read is LOGFILES.CAB, and occasionally XPCREATE.LOG (If LOGFILES.CAB was not created due to a critical error): attaching or quoting the other files rarely does any good, and just annoys me ...

Your welcome, phasley! Part of the problem is that some of the older hotfixes are changed or removed, and there is just too much testing involved to keep the SP1 list up to date.

I'll try again ... soon! Thanks, it_ybd, for the input.

Cool: I get to be the first to post. Thanks for keeping us all up to date, Aaron. Nice small list ... to be continued!

Welcome to MSFN, gcwhite1! It looks to me like the problem is that you have included your SATA/RAID files in the CD source, and not in the FILESCD (in this case, FILESCD\$OEM$\$1\DRIVERS\006_hpt3xx) directory. Note that you shold be starting with an unadultered Microsoft CD. Give that a shot, and post back your results. EDIT:: If you are refering to TXTSETUP.SIF when you say SIF, XPCREATE will edit that file: you should not. EDIT AGAIN:: Happy Birthday, Old Man!

Thanks, krismark. That's basically what XPCREATE does, and those are the files I recommend, with the exception of WMP10, because it was not out when I last updated. It will be there soon ...

Thanks, frankiboy_01. I'd say that covers it. I will be updating the lists to SP2 for all languages ... soon. For now, I would have to say that the pre-SP2 lists are "unsupported".

First, make a "FailSafe" CD using only files listed under Current Hotfixes from the Web Site (DO NOT include the drivers: use the F6 method). Once that works, include the SATA/RAID drivers ONLY. If that works, add the rest of you files until you find the one that causes the error. If you already have the error at that point, post the LOGFILES.CAB file from the NEWFILES directory.

Don't be confused ... just don't be fooled by the need of consistency. You'll be OK either way ... for now.

Unbelievable as it may seem ... I'm not sure a meager 2.5 Gbytes is enough. However, it looks like you have closer to 4 Gbytes free after cleanup, and that should be OK. I don't know what to tell you except try another disk or PC. Alternatively, try another program (Nero, Easy CD) to create the ISO from CDROOT. Please do post if you find the problem or solution.

I've never tried the floppy method (I think I burried all my old floppies), but I believe you need to call WINNT.EXE (or WINNT32.EXE) with parameters if you don't name it WINNT.SIF. Then again ... guess I may have to get a shovel and dig up my floppies to test.

I'll answer this one in your next thread ...

No problem: I was just confirming the validity of the file.

Someone in this forum posted a good codec pack, that is just the files, a .reg file and a .cmd script. Personally, I add the ones I need, and register them with regsvr32, and they work great. Clean, simple, and fully configurable.

No, it is irrelevent. No QCHAIN because ... I haven't got around to adding it. It is probably not needed most of the time, and certainly not needed yet: there are no hotfixes included, just updates.

I'll pass along my respect for another Batch Coder! If I may be so bold as to make a suggestions ... Use IF /I "%VARIABLE%"=="Y"and both Y and y will work. The /I is the IgnoreCase switch. Sorry ... I couldn't help myself! Keep up the good work, and don't let others tell you what/how to code!

Nah ... that would take all the fun out of it! (I'm still debating/touing with these options, thus they are "unsupported") DOPATH=Update OEMPnPDriversPath in WINNT.SIF QLOG=QCHAIN Log File Path SLIPMDC=Slipstream MDAC uUpdate SLIPSPK=Slipstream Service Pack

Just leave everything as it is: XPCREATE will see the files there, verify the MD5 values with the ones from the downloaded hotfix list, and take care of the rest. I may update the list next week for (at least) the DotNet 1.1 SP1, and (possibly) WMP10.

Accepted.

I know: there is no way for a member to delete unwanted posts! Here to remind you in perpetuity!

Well, that's too bad ... I'll test this out in a week or so, and see what I can come up with.

You are welcome! (Don't forget to remind me later ... )

For what it's worth ... I noticed the option to only save as bitmap if the file is not found in the cache. I assume that since it cannot find the original file, it will allow you to save the image from the screen, which would need to be in bitmap form. That also make some sort of sense for the the "View Source" option: if it cannot find the cached version, it cannot show it to you. Perhaps playing around with the cache will reveal something. Sorry I can't tell you more: I use 2003, and it's been a while since I've seen this behaviour. Just throwing some ideas at 'cha.