htc

please take contact with the author of easyboot Otherwise(if you use the regular method) we have enough discussions, also recently.

CDRecord-2.0(former CDRTools) by Joerg Schilling (really Jörg Schilling if you have ISO-8859-1) home page: http://www.fokus.fhg.de/research/cc/glone/...te/cdrecord.htm

I think we've talked about "unattended installation of windows xp" in "multiboot forum", thus the file winnt.sif MUST BE obligatory. So I really donot know why it was for you unclear.

First, I've never used your tool, also never took a look the the screenshot. Second, you self have commented the options list of the cmdline programm, in which the "hide"-options are "not included", here is the evidence: Please donot explain "why"dose not your tool included them - for me only the result is decisive - If your tool has them, I'll try it, if not, I'll let it be. This is absolute objective, not hard, nor offensive.

First, I was never offensive(or have you ever readed some of such things?) Second, instead of offensive, 1. I've highly appreciate his work, 2. I've helpen him to complete/concreting the "feature list" of his work, it took me also time to do that. Third, I've only said "what a pity that the options which may interesting for ME are not included". So only for ME. Anyone else can still find that tool interesting(now you can see the "feature list" and know what you'll get before you download/install/start it)

Use the new version of the freeware cdrtools which supports the gerneric dvd writer for iso burning.

I've only used the bcdw plugin for cd shell or boot scriptor, in that case is the loader.bin in boot folder. have you changed the the path in txtsetup.sif too? how many times? In my case it was total# -3 !

good tip

the tool must be installed to your windows. the iso image file can be leave on the dvd.

BCDW v2 patches the setupldr.bin "on-the-fly" during the loading proccess. I recommand you load the patched boot sector instead. I've created a multiboot AIO Windows XP unattended install CD with diffrent original I386 folder at the root of the CD, but only one $OEM$ folder, thus the "common used" folder "drivers"/"install" for all OS version, and with BCDW 1.5z, and monthes ago. The advantage of BCDW v2.0 is you can use the new cd shell v2.1 and create mouse supported menu structure. I'm working on it and will post the results here in forum. The current CD(w/o mouse support, but with interactive menu via arrow keys) iso image is only 600MB in size but contains: 1. 8 multiboot option, at boot time to select which windows and how many applications/languages would be istalled 2. Upgrade possible, from Win9X/ME/2k/XP 3. Integration of almost all driver of Chipsets, RAID/SATA-RAID, video cards, audio cards,NIC, USB/PCI/DSL-Modem 4. Registry tweaks and unattended install following applications: Total CMD 6.03a, Screensaver Aquarium 2.0, Hardwood Solitaire 3.0, MS TweakUI, Flashplayer 7.0, Acrobat Reader 6.01, MS JavaVM v3810, MS .NET FW 1.1 SP1, winrar, multimedia/divx codecs pack, RealPlayer 10.0, WinDVD 6.0, Nero 6.3.25 UltraEd., Office XP SP2, WinFax 10.02

If you understand it, why did you try to burn a (multiboot-) cd iso image on usb stick?In my post I've point out it is impossible to such thing. Your post:

In fact I dont think the knoppix cd would be for windows(xp/2k/2k3) user usefull either. I want to only point out the fourth way....(other than the three ways) I use the BartPE(with many my selfmade plugins) + UBCD(v2.4) multiboot. Knoppix only for my hdd-installtion.

The reduced source way is not really needed.... also the pain to get the boot folder is superfluous: 1. to reduce the size, you can use nLite 2. to avoid to get the boot folder files, just copy and rename the i386 folder of the original to the target cd root, and than follow my post in this forum: http://www.msfn.org/board/index.php?showtopic=31844

Another option is the knoppix boot cd, at present v3.6 akademie live! release. It's a userfriendly Linux with very fast booting and hundres of installed free software inkl. hardware diagnose, file recovery and also office programs.

Natürlich verstehe ich deine problem! Auf dieser Idee ist man schon viel früher gekommen! Short answer for your question: you have to hex modify the boot files(boot sector+setupldr.bin) and text-modify the txtsetup.sif - the BartPE can boot without modification because it used very few function of setupldr.bin, but the windows setup used it full. I've created a multiboot AIO Windows XP unattended install CD with diffrent original I386 folder at the root of the CD, I named them as "I386", J386", "K386"... The advantage of such AIO setup CDs is you can still use it as "Upgrade/Update-CD", not only for a clean boot installation.

I have said in my prev. post , the options with "hide-xxx" are very interesting, but unforturnitly all such options are in your implementation "not included". These are the functions which cdimage.exe not has and thus for me interesting.

You know sure what P2P means?

I wonder why are there so many people who ignored my prev. post totally! (too lower IQ to understand it?) I must quote it again: All what you quoted website talked about only usb-single-boot, but our themen is usb-multi-boot ! If you dont understand single-boot, how can you discuss multi-boot! If you cannot walk, sure you cannot run! In my post I've clearly point out why the multiboot utility for CD cannot work on usb device. I've also point out what is possible,.

OK, I have mirrored the original website with all downlads,demos, ducumentations... Here is it: http://163.29.16.20/germany/bcdw/ Sorry for the delay, have hun! P.S.: Please don't post this link on other forums or sites without my permission

Sorry that I've forgot to mention that I have the bcdw 2.01a on my home computer, but my home computer dose not have the access to that site(as admin), so I can only upload it when I go to my company again - that means, on Manday. So the word "tomorrow" meaned actually "next working weekday" so that is Manday. Sorry for the inconvenience, perhaps I can find a substitution on sonday, but not sure...

those floppies are only needed when the target PC has NO cd drive. But there are much more PCs without a floppy drive than PCs without cd drive(<0.01%).

If someone is to busy I can take time to count: Features that are not supported(jet): -nobak Do not include backup files - not included -no-bak Do not include backup files - not included -abstract FILE Set Abstract filename - not included -biblio FILE Set Bibliographic filename - not included -cache-inodes Cache inodes (needed to detect hard links) - linux feature, see -duplicated-once for Win32 -no-cache-inodes Do not cache inodes (if filesystem has no unique unides) - irrelevant -check-oldnames Check all imported ISO9660 names from old session - irrelevant, we are doing no multisession -check-session FILE Check all ISO9660 names from previous session - see previous -copyright FILE Set Copyright filename - not included -debug Set debug flag - not included -eltorito-alt-boot Start specifying alternative El Torito boot parameters - not included -B FILES, -sparc-boot FILES Set sparc boot image names - irrelevant on x86 -G FILE, -generic-boot FILE Set generic boot image name - irrelevant -sparc-label label text Set sparc boot disk label - irrelevant on x86 -C PARAMS, -cdrecord-params PARAMS Magic paramters from cdrecord - irrelevant -dir-mode mode Make the mode of all directories this mode. - not included -D, -disable-deep-relocation Disable deep directory relocation (violates ISO9660) - not included -file-mode mode Make the mode of all plain files this mode. - not included -f, -follow-links Follow symbolic links - linux only, see -duplicates-once for Win32 -gid gid Make the group owner of all files this gid. - linux only -graft-points Allow to use graft points for filenames - not included -hide GLOBFILE Hide ISO9660/RR file - not included, can be passed as optional parameter -hide-list FILE File with list of ISO9660/RR files to hide - not included, can be passed as optional parameter -hidden GLOBFILE Set hidden attribute on ISO9660 file - not included -hidden-list FILE File with list of ISO9660 files with hidden attribute - not included -hide-joliet GLOBFILE Hide Joliet file - not included, can be passed as optional parameter -hide-joliet-list FILE File with list of Joliet files to hide - not included, can be passed as optional parameter -hide-joliet-trans-tbl Hide TRANS.TBL from Joliet tree - not included, can be passed as optional parameter -hide-rr-moved Rename RR_MOVED to .rr_moved in Rock Ridge tree - not included -gui Switch behaviour for GUI - does this works at all ? -i ADD_FILES No longer supported -jcharset CHARSET Local charset for Joliet directory information - not needed if -output-charset CHARSET used -L, -allow-leading-dots Allow ISO9660 filenames to start with '.' (violates ISO9660) - this is for linux hidden files, not needed -log-file LOG_FILE Re-direct messages to LOG_FILE - not needed -m GLOBFILE, -exclude GLOBFILE Exclude file name - not included -exclude-list FILE File with list of file names to exclude - not included -pad Pad output to a multiple of 32k (default) - not needed -no-pad Do not pad output to a multiple of 32k - not needed -M FILE, -prev-session FILE Set path to previous session to merge - not needed -new-dir-mode mode Mode used when creating new directories. - not needed -force-rr Inhibit automatic Rock Ridge detection for previous session - not needed -no-rr Inhibit reading of Rock Ridge attributes from previous session - not needed -no-split-symlink-components Inhibit splitting symlink components - not needed -no-split-symlink-fields Inhibit splitting symlink fields - not needed -path-list FILE File with list of pathnames to process - not needed -print-size Print estimated filesystem size and exit - not needed -quiet Run quietly - can be passed as optional parameter -s TYPE, -sectype TYPE Set output sector type to e.g. data/xa1/raw - not needed -split-output Split output into files of approx. 1GB size - not included -T, -translation-table Generate translation tables for systems that don't understand long filenames - not included -table-name TABLE_NAME Translation table file name - not included -ucs-level LEVEL Set Joliet UCS level (1..3) - not included -udf Generate UDF file system - not included -dvd-video Generate DVD-Video compliant UDF file system - not included -uid uid Make the owner of all files this uid. - linux specific -U, -untranslated-filenames Allow Untranslated filenames (for HPUX & AIX - violates ISO9660). Forces -l, -d, -L, -N, -relaxed-filenames, -allow-lowercase, -allow-multidot - not needed -use-fileversion LEVEL Use file version # from filesystem - not included -version Print the current version - not needed -volset ID Set Volume set ID - not included -volset-size # Set Volume set size - not included -volset-seqno # Set Volume set sequence number - not included -x FILE, -old-exclude FILE Exclude file name(depreciated) -hard-disk-boot Boot image is a hard disk image - stil no proper image creator exist - not included -no-boot Boot image is not bootable - not needed -XA Generate XA directory attruibutes - not needed -xa Generate rationalized XA directory attruibutes - not needed -z, -transparent-compression Enable transparent compression of files - linux specific Features that are supported: -A ID, -appid ID Set Application ID - included -b FILE, -eltorito-boot FILE Set El Torito boot image name - included -c FILE, -eltorito-catalog FILE Set El Torito boot catalog name - automaticaly constructed -d, -omit-period Omit trailing periods from filenames (violates ISO9660) -included -input-charset CHARSET Local input charset for file name conversion - done automaticaly -output-charset CHARSET Output charset for file name conversion - included -iso-level LEVEL Set ISO9660 conformance level (1..3) or 4 for ISO9660 version 2 - included -J, -joliet Generate Joliet directory information - included -joliet-long Allow Joliet file names to be 103 Unicode characters - included -l, -full-iso9660-filenames Allow full 31 character filenames for ISO9660 names - included -max-iso9660-filenames Allow 37 character filenames for ISO9660 names (violates ISO9660) - included -N, -omit-version-number Omit version number from ISO9660 filename (violates ISO9660) - included -o FILE, -output FILE Set output file name - included -p PREP, -preparer PREP Set Volume preparer - included -P PUB, -publisher PUB Set Volume publisher - included -r, -rational-rock Generate rationalized Rock Ridge directory information - included -R, -rock Generate Rock Ridge directory information - same effect as previous in mkisofs version used -sort FILE Sort file content locations according to rules inFILE - included -sysid ID Set System ID - included -relaxed-filenames Allow 7 bit ASCII except lower case characters (violates ISO9660) - included -no-iso-translate Do not translate illegal ISO characters '~', '-' and '#' (violates ISO9660) - included -allow-lowercase Allow lower case characters in addition to the current character set (violates ISO9660) - included -allow-multidot Allow more than one dot in filenames (e.g. .tar.gz) (violates ISO9660) - included -v, -verbose Verbose - included -V ID, -volid ID Set Volume ID - included -no-emul-boot Boot image is 'no emulation' image - included -boot-load-seg # Set load segment for boot image - included -boot-load-size # Set numbers of load sectors - included -boot-info-table Patch boot image with info table - included following are not clear -stream-file-name FILE_NAME Set the stream file ISO9660 name (incl. version) -stream-media-size # Set the size of your CD media in sectors -duplicates-once - if two files have the same MD5 hash, just one copy goes to ISO, other is a hardlink -force-uppercase - uppercase all files and folders

I still would like to know: 1. which options are supported 2. which options are usefull, but not jet supported 3. which options are "useless" thus will never be supported Please take the attention that we talk about YOUR TOOL, the GUI for mkisofs.exe, not the options of mkisofs.exe, please answer concretely. EDIT: perhaps you've answered part of my question, but as your last post begined with I could not take it as the supported options of your tool, I MUST take it as the options of the original......

the usage is very simple - no advice needed I think.

My recommendation, do a clean install at first, is very important: during the setup of your favourite application, many registry will be modified, the autoinstall will note all the changes and try to rebuild afterwards. If you take the capture at a different envirement, may some unwanted/usless registry item be modified, and afterwards during unattended install there is no such registry item in your clean envirement, thus the autoinstall cannot rebuild such change, the unattended setup then will be paused(and give an error message out, waiting for replay/unse interaction...) alles klar?