|
Post Number: 11
|
tim
Group: Members
Posts: 32
Joined: May 2004
|
|
Posted on: Nov. 09 2004,06:01 |
|
|
Here's a liitle picture showing the directory structure as I have it. This has beed fully tested to work OK.
Attached Image
|
|
|
|
Post Number: 12
|
rtfm
Group: Members
Posts: 13
Joined: Nov. 2004
|
|
Posted on: Nov. 09 2004,12:42 |
|
|
Gotcha, makes more sense now, just wanted to clarify.
Thanks for the help!
|
|
|
|
Post Number: 13
|
Rock2000
Group: Members
Posts: 1
Joined: Sep. 2005
|
|
Posted on: Oct. 03 2005,11:02 |
|
|
Quote (xoben @ Nov. 03 2004,08:47) | You can use CDShell this way:
1) Download a simplified version from http://dw.ezbsys.net/boot.zip 2) Extract it to disk1\, a folder named boot will be added there boot\moudles boot\cdshl.bin boot\cdshell.ini 3) Copy your disk image (xxx.img for example) to disk1\boot 4) Edit cdshell.ini, change the first line to memdisk /BOOT/xxx.IMG 5) Save the attached file (cdshldr.bin) to disk1\ezboot 6) Use 'run cdshldr.bin' to load your image |
It can't work with Windows ME boot image file.
|
|
|
|
Post Number: 14
|
EvilBetty
Group: Members
Posts: 16
Joined: Jan. 2004
|
|
Posted on: Feb. 07 2006,16:18 |
|
|
I posted a similar post in the UltraISO forum (http://forum.ezbsystems.net/cgi-bin/ikonboard.cgi?act=ST;f=2;t=1220), but since process is now having issues with this ISOLINUX method I thought I would post it here as well.
I am trying to add a new Ghost 8.3 bootable GhostCast ISO from Symantec, and the current Dell 32bit Diagnostics ISO to my EasyBoot disk.
[xoben] has been a tremendous amount of help getting me this far. Following his instructions I used the BIF files instead of the ISO files and followed the rest of the above procedure.
This method works great in my VMWare / Virtual PC session. Both Dell 32 Bit Diagnostics and the Ghost Boot CD, boot correctly.
Unfortunately the CD's did not work on any PC I have in house (12 Dell models from GX-110's through GX-620's desktops, and laptops from C600 - D610). None of them will boot the ISOLINUX sessions, but freeze at a different points. Some freeze at a black screen. Others freeze imediately after the ISOLINUX version is shown with some "DL" code.
Code Sample | ISOLINUX 2.11 08/18/2004 Copyright (C) 1994-2004 H. Peter Anvin isolinux: Starting up, DL = 82 |
Google resulted in the following thread that made me susspect the ISOLINUX version. http://www.911cd.net/forums....c=10612
But after updating your process using the new ISOLINUX.CSM and the new MEMDISK module, it still freeses with either a blank screen or a new message of:
Code Sample | ISOLINUX 3.07 03/01/2005 |
Google resulted in the following thread(s) when looking for other persons have this problem. http://www.911cd.net/forums//index.php?showtopic=15481
I am at a loss... Not really sure how to proceed at this point.
Any further advise you, or any other helpful party may have would be greatly apprecated!
Thanks!
|
|
|
|
Post Number: 15
|
Tattenbach
Unregistered
|
|
Posted on: Feb. 15 2006,08:33 |
|
|
Just a silly question?
where is isolinux involved? Do the Dell images boot from it or are you using it because somebody recommended isolinux as a solution?
I guess I cannot get a copy of that dell iso, can I?
|
|
|
|
Post Number: 16
|
mionica
Group: Members
Posts: 49
Joined: Apr. 2005
|
|
Posted on: Apr. 02 2006,05:42 |
|
|
@tattenbach memdisk is loaded the same way a Linux kernel is. So, to use it, you need something capable of loading Linux kernels. This would mean, you'd have to use SysLinux or GRUB. Most of us prefer the SysLinux package (btw, memdisk and isolinux are both part of it).
CDShell, on the other side, was required because it knew how to pass an argument to the isolinux command line.
Since the later versions of EasyBoot (5.08+) include another tool, the Bootable CD Wizard (BCDW), CDShell is no longer required.
Actually, because BCDW is far more flexible than CDShell ever was, I would highly recommend using BCDW over using CDShell.
To load disk images with memdisk, you need: - EasyBoot 5.08+ - isolinux.bin and memdisk from the isolinux package, copied to c:\EasyBoot\disk1\ezboot
Then, when you want to run an image, just use the command
CODE bcdw /ezboot/isolinux.bin /ezboot/memdisk initrd=<path-to-image-file> You neeedn't patch anything for it to work; also, note the paths are required; for example, CODE bcdw ezboot/isolinux.bin /ezboot/memdisk initrd=/ezboot/dos/etsd.ima would work, while CODE bcdw ezboot/isolinux.bin memdisk initrd=dos/etsd.ima wouldn't.
Also, there's a patch I made for isolinux.bin (get it here) which allows loading of isolinux.bin, memdisk and/or the image(s) from hidden folders, too. With CDShell (as with direct ISOLinux), this was impossible.
|
|
|
|
Post Number: 17
|
Tattenbach
Unregistered
|
|
Posted on: Apr. 03 2006,05:35 |
|
|
@mionica:
Thanks for the explanation but I already knew that.
Actually my old question was in the direction of helping this person that never answered back. I just wondered why she was using isolinux with that Dell image. I do not know it but I doubt that she would really need isolinux. Hence my question, I might be wrong, but I thought she was using a wrong method. Just that!
MfG,
|
|
|
|
Post Number: 18
|
omprakash
Group: Members
Posts: 1
Joined: Jan. 2009
|
|
Posted on: Jan. 28 2009,09:42 |
|
|
how to integrate hiren boot cd 9.7
|
|
|
|
Post Number: 19
|
balder
Group: Members
Posts: 1942
Joined: Oct. 2008
|
|
Posted on: Jan. 28 2009,17:46 |
|
|
@omprakash
Note: This topic is dedicated to "floppy emulation with memdisk" but anyway, here is a link that might help you: http://www.ezbsystems.com/cgi-bin....=hirens
balder
-------------- Download complete set of scripts including help file HERE Note: Script collection updated 2019-05-19. Scripts mainly support EasyBoot_6.5 or later
|
|
|
|
Post Number: 20
|
pmi
Group: Members
Posts: 1
Joined: Jan. 2009
|
|
Posted on: Jan. 29 2009,21:16 |
|
|
Hiren's 9.7 is using isolinux.
You can use "bootinfotable;run hiren.bif"; hiren.bif is the boot file.
|
|
|
|
|
|
|
|