b0r3d Posted September 10, 2003 Share Posted September 10, 2003 Im a fan of WinISO myself. Simple, easy to use, though lacks the ability to add a file if it already exists, or search for a file. Either of these would be handy in an ISO program because its a pain in the arse to have to find the winnt.sif file amongst all that other crap in the I386 directory.So which one do YOU use? And does it have these options? Link to comment Share on other sites More sharing options...
Unwonted Posted September 10, 2003 Share Posted September 10, 2003 WinISO as well Yeah, you have to delete the file first before you replace it in the ISO. Also, WinISO lets you add boot information to the CD! Link to comment Share on other sites More sharing options...
Bachus Posted September 10, 2003 Share Posted September 10, 2003 Nero. Link to comment Share on other sites More sharing options...
Spheris Posted September 10, 2003 Share Posted September 10, 2003 We use CDIMAGE 2.47and use CDBURN/DVDBURN to write and finalizeno runs, no drips, no coasters Link to comment Share on other sites More sharing options...
Aaron Posted September 10, 2003 Share Posted September 10, 2003 Spheris, do you know why when I create an ISO with Microsoft's CDImage app, using a switch to force it not to change all files/folders to uppercase will cause a file not found error on Windows XP Setup (the file is usbshci.dll or something similar) Link to comment Share on other sites More sharing options...
Spheris Posted September 10, 2003 Share Posted September 10, 2003 Can you give me the full command line syntax?I can get you an answer straight back. Link to comment Share on other sites More sharing options...
Spheris Posted September 10, 2003 Share Posted September 10, 2003 Here's an example syntax for you since I don't see a reply yetC:\CDIMAGE.EXE -lXXPSD2_DI -t04/24/2003,12:00:00 -c -h -j1 (-u1 in the case of cumulative dvr testing) -x -bC:\BOOTIMG.IMG C:\BUILDDIR C:\XXPSD2_DI.ISO Link to comment Share on other sites More sharing options...
Aaron Posted September 10, 2003 Share Posted September 10, 2003 Here's the one I use for Windows XP Pro:C:\CDIMAGE.EXE -lWXPFPP_EN -bC:\xpboot.img -t08/26/2001,02:56:00 -d -h -n -m -o C:\XPCD C:\WXPFPP_EN.ISO-d is "don't force lowercase filenames to uppercase" Link to comment Share on other sites More sharing options...
Spheris Posted September 10, 2003 Share Posted September 10, 2003 Side noteI usually do a run through compile of source files with the non joliet extensions and then dump the files from the resulting image because it removes certain errata from the oem and ansi structures in house.the usb components I'll check on in the next few minutes, we don't build them so there might be a name structure problem (intel provided) Link to comment Share on other sites More sharing options...
Spheris Posted September 10, 2003 Share Posted September 10, 2003 CDIMAGE 2.47 CD-ROM Premastering UtilityCopyright © Microsoft, 1993-2000. All rights reserved.For Microsoft internal use only.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/91,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" file system along with mirror ISO-9660 file system (-n, -nt, -d, -c, or -j1, -j2 options apply to ISO-9660 portion) -u2 encode "UDF" file system without a mirror ISO-9660 file system (requires a UDF capable operating system to read the files) -us 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. -b "El Torito" boot sector file, no spaces (e.g. -bc:\location\cdboot.bin) -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 -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. Also note that Microsoft company information is placed in the image volume header, so don't use this program to generate CDs for companies other than Microsoft.For those wondering what Aaron and I are on about Link to comment Share on other sites More sharing options...
webmedic Posted September 10, 2003 Share Posted September 10, 2003 Also note that Microsoft company information is placed in the image volume header, so don't use this program to generate CDs for companies other than Microsoft.Hm does that mean that it should only be used to make isos for wnindows based instelation cd's or does it mean only to be used by micrsoft internaly for building cd's?I think I know I'm just trying to make sure that the meaning was clear to others. Link to comment Share on other sites More sharing options...
Aaron Posted September 10, 2003 Share Posted September 10, 2003 Anyway, my main gripe with CDImage forcing everything uppercase is that the shortcuts I copy over to my start menu unattendly turn out to be uppercase. But I'm sure making an SFX archive will sort that out as the filenames are left intact in the archive. Link to comment Share on other sites More sharing options...
webmedic Posted September 10, 2003 Share Posted September 10, 2003 thats the way to use your install fu arron. As for me I ran accros a small batch file that creates shortcuts for me. I also ran accross how to make them from an inf file you can guess how I'll be doing my shortcuts if I make any. No more copying for me accept for the ones in quick launch. Well and come to think about it there has to be away to make those with an inf also. Link to comment Share on other sites More sharing options...
Spheris Posted September 10, 2003 Share Posted September 10, 2003 Aaron, Shortcut or any extraneous files with commented alterations either OEM or ANSI should be Placed Last to the compile dir, Compile with the J1 or U1 switch only and ignore the secondary switches as the Joilet format overrides in any case.I use the OEM to ANSI for clarifying purposes in house as the vendors provide some of these filesthe USB file does not reproduce the error here (went ahead and tested just to be sure) Link to comment Share on other sites More sharing options...
Spheris Posted September 10, 2003 Share Posted September 10, 2003 Medic, the tool is for in-house use, trueit does generate an MS header but is NOT the tool used for serialization of the CDs themselves, that is located elsewhere in the disc structure. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now