[boot scriptor] Re: Some Questions
- From: "Doctor xp" <doctor_xp@xxxxxxx>
- To: <bscript@xxxxxxxxxxxxx>
- Date: Thu, 9 Jan 2003 22:11:00 +0200
----- Original Message -----
From: "Daniel Guelleken" <dg@xxxxxxxxxxxxxxx>
To: <bscript@xxxxxxxxxxxxx>
Sent: Thursday, January 09, 2003 4:29 PM
Subject: [boot scriptor] Some Questions
>
> Hi!
>
> Till now im just reading but now i think it is time to ask some questions
> (hoped someone els had the same problem)
Don't hope someone have the problem, hope that someone have the answer ;-)
>
>
> 1.
> I have read the discussions about the use of isolinux for loading
diskimages,
> but somehow it does not work for me.
>
> Example:
>
> My floppy images are in /floppys so if i type in "Isolinux
/floppys/toms.img"
> ig get the error massage "Cannot load disk image (Invalid File)"
>
> The same happens if i copy the image to the Isolinux directory and type
> isolionux toms.img.
>
> This happens with all of my images.
>
>
> I want to try the Isolinux Disk emulation because Diskemu does not work
with
> all of my Diskimages, Memdisk works with all my Images but it does not
work on
> every computer.
>
Hmm, ISOLinux isn't actually an alternate emulation method, it just
initiates the BIOS built-in floppy emulation, the problem is that the
implementation of Bootable CD specification is very bad in most BIOSes, this
is one of the original reasons we started the MultiBoot CDs projects.
My opinion, don't bother playing with ISOLinux, and just try to suit your
needs with both DiskEmu and MemDisk.
>
>
>
> 2.
> I own a laptop that boots with bootscriptor but it takes endless to boot a
> Floppy image (several minutes), it happens with Memdisk and with Diskemu
also,
> i were not able to test with Isolinux.
>
> Is there a way to (maybe) find out what makes the booting take so long?
>
> The Bios of that laptop is a "MobilePro" or something, i can write down
exactly
> if it may help?
>
>
> 3.
> This is maybe a little bit OFF-Topic but i will ask anyway:
> I want to create a (Boot)CD that has files on it that have really long
> filenames of about 100 Chars.
> As soon as i have figured out MKISOFS only allows a Maximum of 37
Characters
> for filenames.
>
> I already burned this CD with a Microsoft tool called "Oscdimg.exe"
> Whis is able to create this Image, but it is a Win XP executable and does
not
> work under Win 95, 98, ME.
>
> I dont know how this program makes the ISO, but the CD is Readable on
every
> Windows Computer with the full long Filenames.
>
> I Know that this CD Cant use Joilet for Filenames, but what is it using
> instead?
>
> By the way: This CD is Windows PE (Preinstallation Enviroment) witch is a
mini
> windows Based on the Windows XP Kernel and it can run from a CD, it is
onla ca.
> 150 MB big.
>
You are using Mkisofs 1.15a27 or erlier, try using Mkisofs 1.15a40 it
supports a new paramater '-joliet-long', this allows the extra long Joliet
filenames.
If you can't find the updated version, download BCD 1.1.1 from
www.nu2.nu/bcd/ and get the mkisofs.exe executable from the bin folder.
The CD uses non-standard joliet extensions that permits 127 characters (I
donna know, maybe the full 254 characters), but they are part of the Joliet
standard.
BTW: This release solves the same problem in ERD Commander 2002 (which is
based on the same WinPE environment discussed above).
>
>
> Hope you forgive me my bad English.
>
> Its nice to be in this List ;-)
>
> bye!
>
============================================================
Boot Scriptor mailing list -- http://www.bootscriptor.org
Change your subscription options at: //www.freelists.org/list/bscript
Other related posts:
