Bâshrat the Sneaky

prob 1: I'm sure it's possible to create a DVD install out of the default 2 CD install. And... if you were planning to use a 2CD install... it wouldn't be unattended... prob 2: this is an easy one... Just set autopartition=no and select the partition yourself, then you can delete the old Windows installations simply by formatting them! prob 3: well... check #2

Err... Why not just use the built-in method 2 and just add another DriverPack for your own needs? That's ALOT easier! Just select method 2 in the batch files. To create your own DriverPack: -make a DP folder and put your drivers inhere (in ANY subfolder below it) -7zip the DP folder -rename the file to 'DriverPack_*.7z', where you can replace the asterisk by anything you like -put the file in the DriverPacks folder of the DriverPacks BASE. -done! The DPs BASE will automatically slipstream your own DriverPack!

Why not just leave the things the way they are? You're making it unnecessary complicated!

Please use code tags next time! viasraid.sys = 1,,,,,,3_,4,1 should be viasraid.sys = 1,,,,,,4_,4,1 and did you put the viasraid.sys file in cabbed form in the I386 folder?

Again a nice job, XPero! : But maybe you should update the topic title?

@Lucius Snow: thanks @BaTLeZone: it may work in some cases, but I will NOT guarantee you that. It's clearly mentioned in the ToS (Terms of Use), that these DriverPacks are built for Windows XP ONLY. And it should work fine with XPcreate, but can't guarantee you that either. I never used it, so I have absolutely no idea. IF you try it, use my DriverPacks after you've completed the XPcreate process!

Hmm... When I get home, I'll compare this with the entries I use and if it's not identical, I'll change it to the ones mc134 posted! (You again, mc134 )

Well... it would definetely help if you'd tell us what method you used. What guide you used. What changes you made to the txtsetup.sif, to the winnt.sif, maybe to the txtsetup.oem file? Where you put the files. So... please post the above! (not completely, only the parts you changed...) BTW... Welcome to the MSFN forums!

LOL... This has been posted soooooooooooooo many times before! You can NOT test if your drivers work in any emulated pc environment, nor VirtualPC, nor VMware! So if you want to verify if the drivers you added are working, you'll have to test it on a real machine! (you could make a separate partition to test this)

OK... this must be a language issue I think. I will try to find a method how we can find the exact problem.

And all of a sudden I noticed this: C:\CD1\$OEM$\$$\system32\cmdow.exe Accès refusé. From WHERE EXACTLY are you executing my batch files? I may hope NOT FROM WITHIN youx UWXPCD?

Yes, it CAN tell you: just open the original file and go to File > Save and see which encoding is used by default: THAT's the encoding.

Well... I don't remember well if it was hardcoded in the fake setup.exe, but I think not. Did you add rename commands to the RUN_ME.cmd as well? Cause there's already a 'OEM' folder in the Methods_Vxxx.7z archive...

Well... it *should* be compatible! It works for the Dutch version, so why not for the French or the German? I think this must be some file-encoding issue... Could you tell me which file-encoding is used by default in: -unedited dosnet.inf -unedited txtsetup.sif

Errr?? Are you VERY sure? And from what folder are you executing the batchfile?

In virtual pc you won't get any errors... You have to test it IRL...

True, you WILL get errors. BTW.. you forgot to post which version you used of the DPs BASE.

1) A number is not even required... It's just to force setup to search through the drivers in the order you specify. Microsoft recommends it, but for 99% of us it's pretty useless. 2) You need the .inf file PLUS all files that the .inf file uses. To find out _which_ files the .inf file needs, open the .inf file with notepad and go to the [sourceDisksFiles] section. All files listed here are required. A small note: the nForce audio utility requires to be repackaged to be installed silently! 3) You don't need other things there. And... welcome!

To add your own drivers, isn't very hard. I assume you want to use Pyron's method? (that's method 2 in my DriverPacks) 1. make a folder DP, put ALL drivers in this folder! (you can use ANY folder structure, as long as its in the DP folder) 2. 7zip the DP folder 3. Rename the 7zip file to 'DriverPack_*.7zip', where you can replace the asterisk by just anything. 4. Move this file into the OEM folder at your disk. (or even into the DriverPacks folder of the batch files, it will process this one too!)

d1 = "VIA RAID Combo Driver Diskette", \RAID\winxp\VIAMRAID.SYS, \ d2 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\winxp\viapdsk.sys, \ Well... those are still subfolders of which you have to get rid...

The maximum length of the OemPnPDriversPath is 4096 characters. That's also the reason why I prefer 'DP' instead of 'Drivers' and 'M' over 'MassStorage' etc. If I wouldn't do that, the limit would have been exceeded LONG ago...

It's just a method, it will work for ANY driver

What error did it generate? A txtsetup.oem error? Well, that error has been fixed! There's NO REASON AT ALL why the batch files wouldn't work on Win2k...

@laza: thanks, interesting info @ZileXa: yes, you can!

@dlevens: the original IBM driver did not work for you either? Also, I already have included the IBM SoundMAX drivers! pfffff You may try removing the DP\S\R folder, but I don't know if it will help...