webmedic

not only that but while working on cooker for mandrake the last few years we found out some cdrom droves dont like to boot from 700 meg iso's. Well that is if you have close to 700 megs of data on them as soon as we backed off to 650 meg iso's all was good again.

well the hotfixes being slipstreamed is different than the inf thing and can be done seperately. You could even install the hotfixes with an inf file if you so chose. As for the long time it only seems to lag like tahat under virtual pc on real hardware it installs rather fast. like about 5 or 6 minutes is all. thats on a xp2500 with 512 megs ram but please do remember under virtual pc it's like running a 1gig or so at the most since it shares resources with your runing os. One more thing if you like i could whip up an inf to install hotfixes also it would be rather easy.

no sorry to explain if you are doing it from cmdlines.txt and your files are only under $OEM$ like you mentioined above then your are fine my post said this $OEM$\$1 $OEM$\$$ you will not be able to find those dirs. As long as it is all under $OEM directly like you explain and as long as all your stuff is installed from cmdlines.txt then you are ok. The only place were the $OEM can be accessed is from cmdlines.txt. I hope that clears things up. By the way this is waht I'm going to try next. I will still have a install dir and and a drivers dir on the hard drive but most everything will stay on the cd. I'm jsut trying to get my inf installers to run more than one at a time and then I'm going for this method also. I should be there sometime tomarrow.

if you look the inf was done for you the systax is easier and you only need to change a few lines. I'm glad you like your girlfriend I love my wife also.

and um like it can do everything yours can do the syntax is a little different is all. Some find it easier and a few dont so be it. Besides I have provided scripts for everybody there is nothing to rewrite other than what apps they want installed just the same as you method.

nope that makes you one of those others. I dont personally care what they use but so far a few have found somethings usefull I'm just trying to share is all.

not sure but it does not do it that way and another thing something about the installer doesn't like dirs with $ in them so it would be really hard to get to it on the cd anyway if it was under any dirs that had $ in them.

for those interested the poll was here http://board.MSFN.org/index.php?showtopic=8640 Now I ddin't hold a gun to anybody or anything i really had no idea how many were using it untill I saw that poll. So you two are two of only three that do it this way.

nope not the only just the best. From the little pole done I think most would agree also. PS. I didn't do the pole.

ok try now It's at full 777 so there should not be any more problems. I was trying to just grant write and read access but oh well.

doh ok it should be fixed now

actually durring textmode everything under $OEM$\$1 $OEM$\$$ $OEM$\c $OEM$\d etc are copied to your hard drive and when you run your scripts they are being called from the hard drive if under those directories. The only exception is ny scripts right under $OEM$ which are always run from the cd.

for cmdlines text you can only call files right there so that will not work it should be something like this. [COMMANDS] ".\update.bat" then your bat can call other dirs but cmdlines.txt has to stay local. You will need to place update.bat in the same dir as cmdlines.txt

oh good question as far as I know you are still limited to the smallest drive under striping. Smoebody else may know better but the best way to find out would be to try it both ways and when you get to the part in text mode setup were it asks you how you want to do your drives check the size. That should tell you. Let us know.

really try this it will work better and is easier I had isues also for some reason the reg file would not apply. try this. http://board.MSFN.org/index.php?showtopic=8632 this is for installing stuff durring cmdlines.txt but also works durring guirunonce. I use both ways to install apps adn windows updates and stuff. If you have any questions let me know.

no the cat file is only used to register the component for use under windows. Really you should not have to add the inf file either as txtsetup.sif only needs the driver file itself. Thats the whole idea of adding the lines I added to txtsetup.sif it replaces the inf file more or less. That method works for most of the boards out there by the way it's still baffeling to my the inf file would need to be included. If it works though then so be it.

yes that is not installed like the hot fixes and is not a critical update but rather a regular windows update. My scripts are only for critical updates. .net at this time can not be slipstreamed and will not be added untill sp3 for windows xp.

no problem the funny thing is that that inf file should never need to be included like that. Oh well if it works then great. I will add this to the txtsetup.sif in the drivers.cab also. If you could post in the other thread which motherboard this is working on for you and what chip I'll add it to the top of that thread so we can keep a good count of what all it's working on. I would like it ot be a good resource for other also.

I have posted a complete how to in this thread. http://board.MSFN.org/index.php?showtopic=8734 if that does not work for you then we can look at it.

:punk: :excited: ok yes thats cool. Can you say I can see lots of uses for this.

yes I use this to have my themes and backgrouds and other things auto copied over.

so if I read right it loads the reg file for deafult user and then injects this data into it directly? were did you find this thing?

I'm sory but what is that and how do I use it. It does not look like a reg file. Is it a vbscript? or a cmd file or what I dont quite recognize it. I already understand how to ue cmdlines.txt and use it allot.

I know. It's not so rusty if remember stuff like that.

ftp://ftp.webmedic.net/incoming