[Introducing - Unofficial Windows XP SP4]

Something wrong with this Service pack I am also getting a report of this Servive pack as being Trojans within Avira Antivir:

 

Dotnetfx.exe TR/Rogue.37376.27

Ndpsp.exe TR/Rogue.378646.65

Setup.exe TR/Rogue.36864.71

 

Antivir stopped the process of slipstreaming quarantined the files then all sorts of errors proceeded unable to proceed

[FINDCD & SET as VARIABLE in CMD or as batch]

Well Guys I am Blown away,

You certainly know your stuff on this forum, not that is a great recommendation coming from Lamer like Me, but it is a response of appreciation from ME - non the less!

The Variable within the Set CMD reports CDROM1=F: & CDROM2=G: along with other set variables. All I need to do now is instruct the user to insert the OS Install CD, allow it to spin up or use Horst Schaeffers dready as a check maybe, the variable with if exist will locate the inserted OS CD (With a files Check) then from a Wbat menu (front end) copy the files to a folder on my HDD to compile a bootable recovery console CD, the fileset is obtainable from within the Bootdisk\ folder on the OS Install CD.

I have acquired the Win2K Gold .IMG files (OEM) which reputedly by-passes any XP Logon password so this could be an option also.

Some could say why not use BartsPE or UBCD well yes but this is a quick small bootdisk varient that would replace the floppy Boot disk for the Recovery console as many PC users do not have a floppy drive anymore or floppies take an age to load. Batch files could also be written to try to repair the reg or copy files etc to removeable media from RConsole etc.

Barts & UBCD require quite a bit of setting up

This essentially is background info for this posting, thanks guys!

Regards,

ispy

[FINDCD & SET as VARIABLE in CMD or as batch]

Thanx IcemanND & Benners for your prompt replies,

Firstly, IcemanND I did SEARCH SEARCH but regretably missed the third "SEARCH" on the list LOL! Are there any instructions on how to use your little gizmoes as I have run the .EXE files then opened CMD, typed set to list the variables & no variables listed indicate a CDROM drive as far as I can see. Can you let me know how it works & maybe a couple of practical examples to grasp how it works. I have grabbed DETECTCD2.EXE DETECTCD.EXE & DETECTDRIVE.EXE which one best suits the scenario listed in the 1st posting please?

Secondly, Benners I have made the .CMD file & as you suggest it does indeed report the info that you suggest, then you go on to say that if within a batch file I use %~d0 I will obtain the CDROM Drive letter. Will this be a variable or will it find the actual drive letter "if that is the right term to use". Could you provide a simple working example as a guide please?

Will these two alternatives work within 2K/2K3 & XP?

Regards,

ispy

[FINDCD & SET as VARIABLE in CMD or as batch]

Hello All,

Go easy here, cus I am new to this forum site & well a bit of a lamer! Incidentally I am working off an XPPRO OS!

I was wondering whether there is a resonably easy way in NT command prompt of being able to identify which drive letter is being used for your CDROM/WRITER (or DVD Drive for that matter) then designating that drive letter as a variable to instruct the batch file looking in that drive to extract say certain files from an XP/2K/2K3/NT OS install CD. Or if someone knows of a small CMD Util that will do this, all the better? Preferably it will need to be able to work off NT/2K/2K3/XP systems. Not asking for much am I, LOL!

I have tried on various forums including this one & have not found one that will work for me as yet!

Regards,

ispy