webmedic

well for me no I have never got a bsod. Well I get them but not durring install unless bad ram or the ram is overclocked or the cpu is overclocked. Usually it's bad ram or oc'd ram though. I use virtual pc and bare hardware both. I know of vmware but have never that I can remember haveing used it. I never thought it was worth the cost just to run windows in a window. I mean it has enough stability problems running outside of a window. Windows xp is light years ahead of what it used to be though and to make it bettter hardware support is better also. I either use mksofs/cdrecord or nero for making my iso/cd's.

now make sure that you put your whole driver set under $OEM$\$1\drivers\IDE_RAID and then make sure to add the path to your winnt.sif as I've mentioned above in this how to.

just ran accross it once and thought it would be nice to share. Check this page in particular. http://www.crackmonkey.org/faq.html

well that is hte same method I use if you gett it working post you rresults to the other thread so we can keep working sets for as many systems as possible. now did you make sure to add your raid drivers to your oempnpodriver path in your winnt.sif also make sure that it is listed after your motherboard drivers and before your video card drivers in the winnt.sif for the path.

Oh ok well I cant really help you there. I no expert at virtual pc and it simply works for me with no problems.

what steps did oyu use to make your bootable cd? And what are your config files and such?

thanks for the update and yes I forgot myself that it works with my abit board. I'll add that also.

yes they need to be renamed to be 8.3 compatable. The easiest way is to be Q#######.exe or KB######.exe the jscript can be left alone as it is already under 8.3 and wont hurt anything.

Ok I'll atempt to discribe how to add your own raid drivers. I would apriciate knowing which boards you ahave all got this working on and which raid controler you are using. If possible I would also like to keep sets so that others can benefit from this also. We can slowly work throguh them all till as many as we can get to work do work. For the first set I'll post mine. It is known to work with epox 8k5a2+, 8k3a+, and I assume 8k5a3+, motherboards using highpoint 372 and 374 controllers, Gigabyte ga-7vrxp using promise 20276 Shuttle ak35gtr? using high point 372 in both regular and raid mode Aopen ak79D max using promise pdc20375 Sata150. This works both with regular ide drives and sata drives. Soltek using promise pdc20376 sata150. I was only able to get it to work with the sata drive but this motherboard has issues and it is not an issue with drivers as far as I can see. UPDATE VERIFIED WORKING WITH: Abit kd7 raid using high point 372 Abit be6-II using high point 370 epox 8kra2+ using high point 372 msi kt400 These all work with this driver set: Drivers Now If I have forgotten anything let me know. Also to note If there are any questions please post them here. I'm truly interested in getting this working for all of you. Now for driver cab you will find ide_raid extract that and place it into your drivers folder and add it to your winnt.sif like so OemPnPDriversPath="Drivers\nforce;Drivers\4in1442v;Drivers\IDE_RAID;" this will allow you to use the raid controler after you reboot into graphical install mode. For all the files in the i386 place these into your i386 directory. These are the files that will allow you to use the raid controler durring text mode. I have included in the 1386 folder a file callled txtsetup.sif This file works with english windowsxp with service pack 1 slipstreamed. Dont try to use it if you dont have service pack one slipstreamed. If you dont have service pack 1 slipstreemed nto your install please use the guide below. Now for the how to: This is copied from here: http://www.ee.ethz.ch/~slist/realmen/msg00045.html but I have added to it since I read this and this explination is very complete so I have just copied it here ++++++++++++++++++++++++++++++++++++++++++++++++++++ Anyway, in order to thank you all for the work done, I'd like to bring my own little brick to the building, just in case it might be useful... I met the same kind of problem than Alain : wanted to include third-party mass storage drivers to be used during the text-mode part of a Windows 2000 CD-based setup. In other words, I wanted to get rid of the boring "F6 curse". Pierre's tip works great for the GUI-part of the setup but text-mode setup repeatedly ended with the error : "File txtsetup.oem caused an unexpected error (18) at line 1041 in F:\nt\private\ntos\boot\setup\oemdisk.c", no matter where I put the drivers : the root of the CD, $OEM$, I386 or I386\$OEM$. Here's how I got it working : ====================================================================== My example is based on the IBM ServeRAID driver v5.10. I guess it could be easily adapted to other hardware 1. Copy the driver (nfrd960.sys) in the I386 directory 2. Update the file I386\txtsetup.sif, picking parts of the txtsetup.oem file provided on the ServeRAID driver disk, adapted to the txtsetup.sif's syntax. There are 4 sections concerned : [sourceDisksFiles] nfrd960.sys = 1,,,,,,_x,4,1 [sCSI] nfrd960 = "IBM ServeRAID 4M/4Mx/4L/4Lx/5i Controller (Windows 2000)" [sCSI.Load] nfrd960 = nfrd960.sys,4 [HardwareIdsDatabase] "PCI\VEN_1014&DEV_01BD"= "nfrd960" ====================================================================== Comments : -------- 1. I think that, in the text-mode part of the setup, drivers are used in a rather less sofisticated way than under the GUI part. That would explain why there is no need (in this part) for the .dll, .cat or .inf files (and the parameters stored in them). 2. But being loaded during the text-mode doesn't mean installed on Windows 2000. So you still have to install your driver in the GUI part, using Pierre's method. 3. For the "Line 2 of the INF file is invalid" error, I suggest to check the following KB article : http://support.microsoft.com/default.aspx?...EN-US;Q304305&; Guesses : -------- 1. I didn't succeeded in loading drivers for the text-mode setup by copying them in the $OEM$ tree. During this part of the setup, the CDFS file system is not yet loaded, so the only character-set that setup is able to read is the ISO9660, which doesn't include "$" In other words I think that, at that time, the directory is read as "_OEM_" :-) 2. During my investigations, I parsed the txtsetup.sif file to see how and where the "retail" SCSI drivers were listed. In the [sourceDisksFiles] section, they are all referenced in the form : driver.sys = 1,,,,,,3_,4,1 I changed the "3_" to "_x" because I noticed that all the files that where not compressed in the I386 directory where referenced this way ====================================================================== APPENDIX - Content of the original TXTSETUP.OEM file (from the ServeRAID driver diskette) : [Disks] d1 = "IBM ServeRAID Device Driver Diskette", \Win2kSrv\driver\i960\NFRD960.SYS, \Win2kSrv\driver\i960 [Defaults] scsi = NFRDWin2k32 [scsi] NFRDWin2k32 = "IBM ServeRAID 4M/4Mx/4L/4Lx/5i Controller (Windows 2000)" # If you hit F6 and specify to load an OEM driver, NT loads the first driver in # the list. If you don't hit F6 and specify to load an OEM driver, NT loads # the last driver in the list. [Files.scsi.NFRDWin2k32] driver = d1, nfrd960.sys, NFRD960 dll = d1, nfrdci01.dll driver = d1, nfrd960.sys, NFRD960 catalog = d1, ibmnfrd.cat inf = d1, oemsetup.inf [Config.NFRD960] value = parameters\PnpInterface,5,REG_DWORD,1 value = parameters\Device,NumberOfRequests,REG_DWORD,128 [Config.IPSRAIDN] value = parameters\PnpInterface,5,REG_DWORD,1 value = parameters\Device,NumberOfRequests,REG_DWORD,128 [HardwareIDs.scsi.NFRDWin2k32] id = "PCI\VEN_1014&DEV_01BD", "nfrd960" ====================================================================== ++++++++++++++++++++++++++++++++++++++++++++++++++++

@djus I'm sorry but I don't seem to be able to find your email. If you could email me just your inf file. That would be great.

o cool I can see that. Good plan I may use that when i get done then but for now for my testing it is easier to just do full unatended with my cd key.

ah ok well enjoy the inf file way. I find it cleaner to deal wiht and it looks almost the same as doing the straight reg hack way.

yes I dont believe mine uses that switch either. Thats really kind of interesting. Might want to check your ram.

default hide what does that do. and if it does not install correctly then it doesn't work I guess.

ah the tick is the inf way you dont get it the other way. or at least I dont think you do. but here is a link about using inf for installing. http://board.MSFN.org/index.php?showtopic=8632 this exact same method can be used for guirunonce also but in that example I do the cmdlines.txt part.

sorry it would have been easier to star on the thread i started. Those folders install\system\hotfix3 needs to have the mdac hotfix in it and then it uses nstall/tmp to extract to durring setup. this was the only way to get mdac slipstreamed I tired amny things first. In my finished script I would have it make all those directories

not sure about that one that has never hapend to me oh also one last thing make sure to unpack your sp1 cab from your i386 dir into files/sp1 this will also update the files in your sp1 cab. Three are quite a few that need to be updated by the way. and also if you dont do this and you copied them over with out doing this then your sp1 cab will be completely empty which is bad I'll try to add better checks for that so this does not happen.

yes also to note if you dont want to use my winnt.sif the raid drivers or the txtsetup.sif for the raid drivers then delete those out of the files folder and they will not be used. One more thing if you put your winntbbu.dll into the files folder it will pack it up for you wile it does everything else. Mostly I set this up as my stageing area I edit everything here and include what I want in the files folder. Then when this script gets done it is all packed and ready to copy into my i386 folder. It's a little les work for me in the long run. When i get done I'll add sp1 slipstreaming and iso building and stuff like that.

ok thanks for the heads up. I'm not really trying to mess with anything iffy and as for my own tuff I do have access to others who love warez and the like but I jsut tell them i cant do that. Nice to know a few of the other things I was thinking about have not caused an issue. As for .net and dx9 I guess I can see the issues here also as this of course is not the way they would like to properly suport it and are worried about getting support calls for things that are not done according to spec. I think at this time the only thing I'm really doing to change things from default though is a custom theme on my desktop and turing quicklinks on by default. The rest is rather standard stuff. I will be carefull to not go over the line and I dont like warez.

lol yes make sure you have the latest versions of your software installed before you try ito install a patch for a version you dont have installed. There is part of the problem. There is no way that I know of yet to slipstream the newer version of ie into the install so there is no way to apply that hotfix since the latest version of ie has not been slipstreamed first. on a side note the script is only for hotfixes at this point and not for apps. this method does not support fully things like dx9 or .net or anything other than critical updates . All the other regualr updates are not ment to be installed this way and it is not my script micrsoft programed them that way. .net is so funny it wont even be integrated untill sp3. They have to completely rewrite it for that also. having said that there are ways to kind of integrate these things but I want the current version stable first before I start adding .net and dx9 and a few other things. The next version will be allot more fun and things for you all to try out. I'll also see if I can provide a way to do a few other things that are not supported right now.

no

well I found in some instances things did not install I could not track it down completetly so iremoved it from doing it htat way and now everything installs correctly the first time. I found something called econsole and it is jsut a wrapper for cmd.exe it allows my with an ini file to place the command propmpt off the viewable area of the screen I think I will use this instead. It also allows for transparent consoles and the like. I think it would look mighy good even if i did have to let it show.

ah much faster. I think i found a way to hide the cmd window also. Let me test it first but I think it will work.

um you did not mean to list uxtheme.dl_ did you? I mean I dont think you mean to list that?

no thats one of the little nigglies. If you use cmdow it will spawn another task that will not work properly. I mean i did get it to hide the window but it also did not install .net or movie maker i think it was. The unstall would just bomb out for those two but the inf file would continue on. It was kind of funny the way it did things. So I want back to letting the window stick up there untill I find another way of hiding that window.