Page 1 of 1

Installing to USB (for V5)

Posted: Fri Jun 05, 2009 5:43 pm
by anoop
I searched the forum and it does not look like this has already been reported.

The batch file to write to the USB seems to be slightly defective and not very clear.

The line 63 should be changed to:

Code: Select all

if not exist "%a1%\ubcd\tools\win32\ubcd2usb\ubcd2usb.cmd" %0 : _error Missing '%a1%\ubcd\tools\ubcd2usb\ubcd2usb.cmd' (script did not run successfully)
from

Code: Select all

if not exist "%a2%\ubcd\tools\win32\ubcd2usb\ubcd2usb.cmd" %0 : _error Missing '%a2%\ubcd\tools\ubcd2usb\ubcd2usb.cmd' (script did not run successfully)
Also the instructions should be clearer to indicate the source path. One suggestion is to put the path just one level above the [BOOT] folder.

Further on a side note, the size of the image has increased such that it no longer fits on a 256MB USB, please let me know if there is a quick hack for that - maybe I can delete / ignore some files I do not need like the antivirus files etc..

This is a wonderful tool and it has saved my skin tonnes of times, please keep up the excellent work.

Posted: Sun Jun 28, 2009 6:23 pm
by Victor Chew
The line 63 should be changed to:
That line is correct, since it is looking for a file on the target to make sure the copying was successful. %a2% contains the target drive.
Also the instructions should be clearer to indicate the source path. One suggestion is to put the path just one level above the [BOOT] folder.
I don't quite understand this. Do you have a more concrete example?

Posted: Fri Oct 16, 2009 1:25 am
by minos
I had this problem when trying to put UBCD on my usb drive... with Vista Sp1 64 Bits.

No problem with XP Sp3 32 bits...

Hope it helps ;)

Posted: Wed May 05, 2010 1:55 am
by migu
This problem occurrs when the end user is not paying attention to the information given when running the ubcd2usb.cmd utility without any parameters from a mounted CD(image). So, by incorrectly starting the script the following way will induce this behaviour:

E:\ubcd\tools\win32\ubcd2usb>ubcd2usb "e:\ubcd" F:

When the correct commandline should read:

E:\ubcd\tools\win32\ubcd2usb>ubcd2usb E: F:

Maybe the instructions given at command line could be improved to reduce the likelyhood of confusing the casual user.

Posted: Wed May 05, 2010 1:49 pm
by Victor Chew
Maybe I am dense or something, but the instructions seem as clear as daylight to me:

Code: Select all

Usage: UBCD2USB (UBCD-path) (USB-drive) [/f]

Examples: UBCD2USB e: f:
 (UBCD-CDROM in 'E:', USB-key in 'F:')

 UBCD2USB "d:\ubcd" f: /f
 (UBCD extracted in dir 'D:\ubcd', USB-key in 'F:',
 format target f:)
Do you guys have any concrete suggestions on how it can be improved?

Posted: Wed May 05, 2010 2:22 pm
by Icecube
Victor, maybe you could change:

Code: Select all

 UBCD2USB "d:\ubcd" f: /f
 (UBCD extracted in dir 'D:\ubcd', USB-key in 'F:',
 format target f:)
to:

Code: Select all

 UBCD2USB "d:\ubcd-extracted" f: /f
 (UBCD extracted in dir 'D:\ubcd-extracted', USB-key in 'F:',
 format target f:)
In UBCD50, there is already a ubcd dir in the iso itself, while in UBCD411, there wasn't. This may have caused the confusion.

Posted: Thu May 06, 2010 12:22 am
by migu
Maybe I am dense or something...
Victor, you are definitely not the one to be dense, but a lazy user might be :) I think Icecubes suggestion will clarify the matter enough.

Posted: Thu May 06, 2010 12:14 pm
by Victor Chew
Thanks! I have made the change. I have realized long ago I am not suitable for working in user-facing positions. :D