Yzöwl

You can escape the command window at any time, if thats what you mean, with CTRL + C [Edit] Are you trying to edit the registry hive, if so which one, why and how? [/Edit]

@ mythosaz I don't know much, if anything about Kix, but I can tell from your file, that it has a fixed volume label, fixed iso name and no rightclick option to create the iso from the folder context menu. I think you'd have been better off posting it with full instructions on its usage etc. in a New Topic.

@MCT Done, sorry for that error! Thanks

@Afterdawn Here you go then! This one is a single right click extension MakeISO It is a simple combination of the previous postings command files, it asks you if you want to make it bootable, and performs the appropriate routine. As a little addition, I have made the option to uninstall this one. To do so, just go to Add/Remove programs and remove its entry from there. Note If you installed the previous inf, and you would prefer ths option instead, no uninstall routine was added to it. You will need to remove the cmd and img folders including their contents from %SystemRoot%\system32. You can also delete CDIMAGE.EXE from %SystemRoot%\system32, as it will be installed by the new inf. To remove the old registry entries, you know where they are from the previous cdimage.inf. I've done this for you, don't expect everything..... [Edit] makeiso.zip updated and replaced, error in inf. (See post below!) [/Edit] [Edit2] makeiso.zip updated and replaced, improved coding to cmd and inf with small fix in cmd. [/Edit2] makeiso.zip

The switches given in the CDIMAGE download on the MSFN's Unattended XP CD - Getting Started page, here were: -h -j1 -mThey have always worked fine for all my UA CDs, and are what most newbies will be using. The only change from those options was that I included the optimize switch. You would be aware of this if you read the original thread as directed in my first post. The files were intended as an aid to newbies, and people sick of constantly altering the cmd file from the Unattended site, whilst testing their compilations. An additional option for creating ISOs for general data CDs was added too for good measure. It must be understood that anyone creating any other type of CD or DVD must check the content of the extracted zip, to check for suitability first. Also for data CDs check the switches available in CDIMAGE first, and ensure that the ones in the cmd file are suitable too. Additionally, if someone wishes to create an ISO of their recycle bin, (which is after all just a folder), or any other folder, then by all means do so, if they don't wish to use this option, then they don't click on it. If someone is incapable of right clicking on the appropriate folder to select the required option, for the intended ISO, then that's their problem, not anyone elses. At present, if I was to right click on my Recycle Bin, I would be given an option to create a compressed archive of it, because it's a folder, what's the difference? For the benefit of anyone requiring the switches here they are: Usage: CDIMAGE [options] sourceroot targetfile -l volume label, no spaces (e.g. -lMYLABEL) -t time stamp for all files and directories, no spaces, any delimiter (e.g. -t12/31/2000,15:01:00) -g encode GMT time for files rather than local time -h include hidden files and directories -n allow long filenames (longer than DOS 8.3 names) -nt allow long filenames, restricted to NT 3.51 compatibility (-nt and -d cannot be used together) -d don't force lowercase filenames to uppercase -c use ANSI filenames versus OEM filenames from source -j1 encode Joliet Unicode filenames AND generate DOS-compatible 8.3 filenames in the ISO-9660 name space (can be read by either Joliet systems or conventional ISO-9660 systems, but some of the filenames in the ISO-9660 name space might be changed to comply with DOS 8.3 and/or ISO-9660 naming restrictions) -j2 encode Joliet Unicode filenames without standard ISO-9660 names (requires a Joliet operating system to read files from the CD) When using the -j1 or -j2 options, the -n, -nt, and -d options do not apply and cannot be used. -js non-Joliet "readme.txt" file for images encoded with -j2 option (e.g. -jsc:\location\readme.txt). This file will be visible as the only file in the root directory of the disc on systems that do not support the Joliet format (Windows 3.1, NT 3.x, etc). -u1 encode "UDF-Bridge" media -u2 encode "UDF" file system without a mirror ISO-9660 file system (requires a UDF capable operating system to read the files) -ur non-UDF "readme.txt" file for images encoded with -u2 option (e.g. -usc:\location\readme.txt). This file will be visible as the only file in the root directory of the disc on systems that do not support the UDF format. -us sparse UDF files -ue embed file data in UDF extent entry -uf embed UDF FID entries -uv UDF Video Zone compatibility enforced -b "El Torito" boot sector file, no spaces (e.g. -bc:\location\cdboot.bin) -p Platform ID for the "El Torito" boot catalog -e Do not set floppy emulation mode in El Torito boot catalog -s sign image file with digital signature (no spaces, provide RPC server and endpoint name like -sServerName:EndPointName) -x compute and encode "AutoCRC" values in image -o optimize storage by encoding duplicate files only once -oc slower duplicate file detection using binary comparisons rather than MD5 hash values -oi ignore diamond compression timestamps when comparing files -os show duplicate files while creating image (-o options can be combined like -ocis) -w warning level followed by number (e.g. -w4) 1 report non-ISO or non-Joliet compliant filenames or depth 2 report non-DOS compliant filenames 3 report zero-length files 4 report each file name copied to image -y test option followed by number (e.g. -y1), used to generate non-standard variations of ISO-9660 for testing purposes: 1 encode trailing version number ';1' on filenames (7.5.1) 2 round directory sizes to multiples of 2K (6.8.1.3) 5 write \i386 directory files first, in reverse sort order 6 allow directory records to be exactly aligned at ends of sectors (ISO-9660 6.8.1.1 conformant but breaks MSCDEX) 7 warn about generated shortnames for 16-bit apps under NT 4.0 b blocksize 512 bytes rather than 2048 bytes d suppress warning for non-identical files with same initial 64K l UDF - long ads used in file entries instead of short ads r UDF - number of ad's is random w open source files with write sharing t load segment in hex for El Torito boot image (e.g. -yt7C0) f use a faster way to generate short names -k (keep) create image even if fail to open some of the source files -m ignore maximum image size of 681,984,000 bytes -a allocation summary shows file and directory sizes -q scan source files only, don't create an image file NOTE: Many of these options allow you to create CD images that are NOT compliant with ISO-9660 and may also NOT be compatibile with one or more operating systems. If you want strict ISO and DOS compliance, use the -w2 warning level and correct any discrepencies reported. YOU are responsible for insuring that any generated CDs are compatible with all appropriate operating systems.

Well unfortunately, I wasn't even a twinkle in this forums eye, when you wrote that message, but I'm sure if MCT, got the basic idea from there, he'll let us know. Still, he should get credit for the idea of having the variable iso and label names. Thats what interested me most in the first place.

@MAVERICKS CHOICE Easiest way would be to add the following command to your cmdlines.txt and keep all the extracted files together within your folder structure. "rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 132 <path to folder>\cdimage.inf" You should also be able to add the same line to any of your batches too!

@nam265 I think that the img file will be fine for those OSes If not, one method to retrieve the appropriate img is this, First, download and install the freeware program 'Isobuster'. Insert your original Windows CD (MCE 2000 XP 2003) into the drive and open up Isobuster. Navigate to the 'bootable CD' directory. In the right hand pane, highlight '<microsoft corporation>.img', (the name may be different depending on which OS the CD is for). Right click it and select 'extract <microsoft corporation>.img' to extract the file.

When creating your unattended CD, CDIMAGE is used by nearly all of us. I know there is a GUI version of CDIMAGE, but most of us would still prefer something a bit easier to work with. Recently I saw a post request, by MCT, he was trying to use a right click context menu command which just created the ISO. A simple idea, and very handy for most of us! In my last posting, on the fore-mentioned thread, I had found a method of achieving the original goal. I've since tweaked it a bit, to allow for spaces in the folder name, and give it a simple installation method. Instructions Download the whichever of the two attached zip files you require, unzip it, right click on *.inf and choose Install. You can now delete the extracted files if you wish, as you will no longer need them. To use it, right click on the folder containing the files with which you wish to create an ISO and select either from MakeISO.zip Build Bootable ISO Build Data ISO or from BootISO.zip MakeBootISO The ISO will be created in the parent directory of the folder you selected. If you have an earlier version of one of the many insarnations of these files, you will be better off uninstalling it from add /remove programs first. Beware some versions may not unistall correctly, due to bugs /errors and some may require a reboot or manual directory deletions too. [EDIT] If you are not running Win2k or higher, or if you intend creating a bootable CD for any OS other than XP some of the files provided may require editing /changing [/EDIT] [EDIT2] MakeISO gives you options for both Data CDs and Bootable CDs (the type we create for unattended installs) Thanks to the 8936 people who downloaded the last version of DoISO, you can download the newest version MakeISO here. Whereas BootISO is for Bootable CDs (the type we create for unattended installs) [/EDIT2]

Copy will only copy files, use XCopy, which will copy directories and subdirectories. e.g. XCOPY /S folder c:\myfolder\ will copy the content of "folder" including sub-directories to "myfolder".

Everything looks to be okay, the cmd shell doesn't have any problems with the > character and your quotes etc are fine. Are you sure that the registry key actually exists? If it does, check that its key isn't protected somehow by the system, and also try it directly from a standard batch just in case its the Runoncex command structure which is having problems translating the > character.

An acquaintance of mine has just installed it along side Spybot and Adaware, and it picked up more than half a dozen things missed by them.

have you tried replacing the start /wait bit with REM------------------------------------------------------------------------------------- REM Setup Firefox Associations REM------------------------------------------------------------------------------------- CALL %systemdrive%\install\Applications\Firefox\Firefox.cmd REM----<snip>

I don't want to sound harsh, but you are asking a lot of questions, all within a short period of time. Read the guides and forums for a week or two, most of these things including your question on this occasion has been discussed. Use the search facility. If you don't like it's results, don't complain, it's because lazy people who want there CD done NOW couldn't be bothered reading and digesting first. They just started posting the same questiions over and over again.

For the extracted msi Command line parameters: /L language ID /S Hide intialization dialog. For silent mode use: /S /v/qn. /V parameters to MsiExec.exe I guess the latter will be these /P password mode /A administrative installation /J advertise mode /X uninstall mode /F repair mode /B cache installation locally

Firewall: Hardware, but if not Sygate Personal Firewall - (free) Anti-Virus: AntiVir - (free) Advanced Windows Tuning (software like tweakXP): (registry editing tools) - (free) Download Utilities: Built in or Extension for Firefox Browser - (free) E-Mail: WebMail - (free with any browser) or Thunderbird - (free) Webdesign: Amaya (free) and Crimson Editor - (free) Graphics Development: Pixia - (free) Hard-Drive optimization tools (defraggers for example): Built-In - (free) and ERUNT /NTREGOPT - (free) Windows error Checking (Like Norton Utilities): Built-In - (free), RegCleaner - (last available freeware version) Antything else that comes to mind: OpenOffice org - (free)

Sorry I forgot about this thread, yes it's the cmd file that needs changing, try this, it works for me! Put this in your inf: HKCR,Folder\shell\MakeBootISO\command,,,"%11%\bootiso.cmd ""%1""" And this for your bootiso.cmd: ::Automatic naming bootable ISO script @echo off SET DIRE=%1 TITLE Creating Bootable ISO Image of %DIRE% ECHO. ECHO Removing any possible attributes set on %DIRE% and its subfolders... ATTRIB -R -H "%DIRE%" /S /D FOR /F %%G IN ("%DIRE%") DO SET LABL=%%~nG ECHO. ECHO Creating ISO... CDIMAGE.EXE -L"%LABL%" -h -j1 -m -o -B%SystemRoot%\system32\xpBoot.img %DIRE% %DIRE%.iso ECHO. PAUSE EXIT For this both the cmd, img and CDIMAGE are all set for the system32 directory. Note: Things dont go quite so well if you have spaces in your foldername, also although the ATTRIB command will work with long filenames, you will need to remember that the ISO label can only accept eleven characters. For best results then, try to keep all folders to be processed to eleven charcters or less with no spaces. You would need to add extra code if you wish to fix the spaces in folder name and character length issues. PS You will also have to create a data.iso cmd and add its respective entry into your inf, using this as a guide, for that right click option too. Hope this helps! [EDIT] I have fixed the spaces problem, and done a little tweaking to create a simple tool for this feature, please see this post, Thanks! [/EDIT]

%01% => SourceDrive:\Pathname (the directory from which the INF file was installed)

example from cmdlines.txt when inf is in same folder as it [Commands] "rundll32.exe setupapi,InstallHinfSection DefaultInstall 128 .\whatever.inf" example from a cmd ECHO Applying Whatever.inf rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 132 "Drive\Path\whatever.inf"

I don't wanna sound like I'm teaching you to suck eggs, but you have got a hacked uxtheme.dll, haven't you?

Did you create the keys in the registry editor, and export them out, then find that the reg wouldn't import? or are you telling us that a REG_EXPAND_SZ key is not working for the SourcePath entries. I doubt that you can just blindly change all REG_SZ entries for REG_EXPAND_SZ and expect them to work! Stick with the CMD or INF methods This would be the INF to match your CMD [Version] Signature=$CHICAGO$ [DefaultInstall] AddReg = Reg.Settings [Reg.Settings] HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Setup,"Installation Sources",0x10000,"%24%\Support\i386" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Setup,SourcePath,,"%24%\Support" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Setup,ServicePackSourcePath,,"%24%\Support" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion,SourcePath,,"%24%\Support\i386"

Glad to help! It may now be a good idea, to remove your reg file, (unless you wish to leave it for others to fix), since it does not really contribute to the thread.

I also believe that full instructions can also be found just a few posts down currently on this foums first page, XP SP2 CD with Slipstreamed SATA/RAID Drivers.

@ SyntaxError Open it up in Notepad, right at the end of your file add a return then Save As... newname.reg with ANSI Encoding instead of Unicode. Now try it, if it works, delete your existing RegTweaks.reg and rename the new one back to suit.

You don't need quotes around your ComputerName at all but, I would guess, that in your [TapiLocation], you will also need: Dialing=Tone AreaCode=<put you area code here> also, if you are adding a section, you will also need the following above it: [branding] BrandIEUsingUnattended=Yes