VCC

FYI: I have a similar problem as - hfrfc - when I choose KtD (using method 2). I wanted to use this function in order to create a ghost image of the computer that can be dropped to different models of PCs. If I choose not to KtD I do not get prompted with the WHQL.

Thanks Siginet, I've confirmed the problem with saving the ISO with the same name as the destination folder and how it exists with other application's saving feature as well. Case closed.

Minor problem; I'm noticing when I go to name the ISO, if I name it the same name as the Destination folder, it goes into the destination folder instead of saving the ISO file. I have to manually add ".ISO" for it to save to that name.

Concerning the DRVINDEX error (I'm just curious): By any chance, have you checked the rights on the file to make sure it isn't set to read only or got changed somehow to read-only? Also, what version of the DPs are you using? How funny, I just noticed I'm labeled as a newbie. LOL ya, ya, I know I'm a newbie to the site. A newbie with 10 years under my belt. I have to laugh.

Just a little good news FYI: I was having trouble with my packs from RC4 where the PC would reboot in the GUI part of setup just as it seemed to be finishing T-30 "Installing Devices". This was happening on 2 out of 3 computers, all computers were different (all Intel motherboards; an Easton P-III, 950Mhz; a D850EMV; and the one that worked was a newer D925XECV2) I couldn't even get success out of a regular XP SP2 CD with the D850EMV, and I could with the Easton. Now to the actual good news: I build a tri-pack using RC5 with the same software I had previously used with RC4 and it worked so far on the Intel D850EMV. I didn't have enough time to try it on the other machines. Thanks again Siginet for all your hard work and late hours coding this, another awesome creation! Keep up the excellent work. Oh, and congrats on the forum.

Thanks Siginet, I get the idea of what to do and will experiment with what I need until the plug-ins come out. I appreciate all the help!

This may not affect many people. What is the chance of having a possible WINNT.SIF selection. Maybe as a plug-in later. This is in case there are different .SIF files for different settings. I personally use three different ones and it would be cool to have that selection at the beginning of the setup disk just as the other selections.

Okay, I'm fired up!!! I killed the Symantec Antivirus (Corp. Ed.) 9.02 and ran the non-WINNT32 version. IT WORKS!!! So far, so good. Without the Driver packs. I'll remove the Mass Storage driver pack and give it another shot without them. Question: Siginet - Do you create your builds without the Mass Storage Driver pack?

With the winnt32 version I'm still getting the error: Error opening file setupldr.bin & txtsetup.sif during the HEX editing portion. I decided to try the User Attended option without the BTS DriverPacks to see if I still received the hptmv6 error, which I didn't, and that leaves me with wondering if it's either my Drivers Pack or my WINNT.SIF file.

Oops, my bad, noticing the 3 in the wrong place. That's STEP 3, not option 3. I guess I need more COFFEE to wake my but... up.

You know, I wouldn't put it past me that I'm doing something wrong myself . I've downloaded the winnt32 version again and tried it again. Still getting the error msg about the hptmv6 file during the winnt32 (Scare) portion of the build. I also noticed that BTS's Driver Pack is choosing the 3rd option instead of the 2nd option that I had asked for originally. I'm still shaky on which option is best for me. I've installed .NET to see if that would make any difference but I still need to try the non-winnt32 version and find out.

I was able to download the winnt32.exe version okay. About to run it now. Thanks Siginet for all the hard work.