Hey guys, I've been trying to figure out how to make a Multiboot plugin that will work for an ISO I've made, but so far I haven't ran into any examples of an MS-DOS image booted from ISO, they are all from floppy images. Now, before someone suggests I just make it into a floppy image, I will say that this is what I used to do - up until I got to Ghost 11.5 which has an EXE that is 2.2MB. That makes it basically impossible for me to include that EXE into an ISO in addition to all the network drivers I'm using.
My solution to this was to make an ISO that uses a bootable floppy image with all the network drivers I want and a boot menu (using the config.sys syntax for the menu) to pick what NIC I'm trying to boot for. MS-DOS would then boot, loading OAKCDROM.SYS and MSCDEX.EXE to use the CD-ROM drive where I placed GHOST.EXE. So a 1.44MB floppy image along side a 2.2MB EXE, and it's all working on a standalone ISO.
From what I've seen, you can directly boot from a floppy image, but when booting from an ISO you have to specify a kernel to use for Syslinux. Maybe I'm just thinking way too hard about this, but am I going to have to figure out how to use Syslinux for this to work or can I boot straight from an ISO with BCDW? Just a bit confused.
Any help would be greatly appreciated!
Full Version: Symantec Ghost 11.5 with Network Support
BCDW supports 2.88MB floppy images.
Ghost EXE - 2.2MB
io.sys - 222k
command.com - 93k
mscdex.exe - 25k
oakcdrom.sys - 41k
msdos.sys <1k
config.sys <1k
autoexec.bat ?
This should leave you with ~300k for network drivers and other files.
but, since you didn't want to hear about a solution like that...
dban
gujin
goback
ntfs4dos
are all examples of bootable floppy images.
Ghost EXE - 2.2MB
io.sys - 222k
command.com - 93k
mscdex.exe - 25k
oakcdrom.sys - 41k
msdos.sys <1k
config.sys <1k
autoexec.bat ?
This should leave you with ~300k for network drivers and other files.
but, since you didn't want to hear about a solution like that...
dban
gujin
goback
ntfs4dos
are all examples of bootable floppy images.
QUOTE (pcuser @ Jul 8 2008, 07:00 PM) 
BCDW supports 2.88MB floppy images.
Ghost EXE - 2.2MB
io.sys - 222k
command.com - 93k
mscdex.exe - 25k
oakcdrom.sys - 41k
msdos.sys <1k
config.sys <1k
autoexec.bat ?
This should leave you with ~300k for network drivers and other files.
but, since you didn't want to hear about a solution like that...
dban
gujin
goback
ntfs4dos
are all examples of bootable floppy images.
Ghost EXE - 2.2MB
io.sys - 222k
command.com - 93k
mscdex.exe - 25k
oakcdrom.sys - 41k
msdos.sys <1k
config.sys <1k
autoexec.bat ?
This should leave you with ~300k for network drivers and other files.
but, since you didn't want to hear about a solution like that...
dban
gujin
goback
ntfs4dos
are all examples of bootable floppy images.
Unfortunately none of those suggestions are going to help me. I have more than that much spaced being used for network drivers (trust me, I've done every variation of saving space that could be imagined, almost resorted to a RAM disk for some things, but it wasn't going to be very good). I don't need a boot disk either, I must have a way of booting from an ISO or this just won't work out at all. No files that are on the floppy image are unneeded, but with all of them plus GHOST.EXE it will be over 2.88mb.
Why not just boot a standard floppy image that maps the cd drive to X: and place the ghost exe file on the cd?
QUOTE
My solution to this was to make an ISO that uses a bootable floppy image with all the network drivers I want and a boot menu (using the config.sys syntax for the menu) to pick what NIC I'm trying to boot for. MS-DOS would then boot, loading OAKCDROM.SYS and MSCDEX.EXE to use the CD-ROM drive where I placed GHOST.EXE. So a 1.44MB floppy image along side a 2.2MB EXE, and it's all working on a standalone ISO.
From what I've seen, you can directly boot from a floppy image, but when booting from an ISO you have to specify a kernel to use for Syslinux. Maybe I'm just thinking way too hard about this, but am I going to have to figure out how to use Syslinux for this to work or can I boot straight from an ISO with BCDW? Just a bit confused.
From what I've seen, you can directly boot from a floppy image, but when booting from an ISO you have to specify a kernel to use for Syslinux. Maybe I'm just thinking way too hard about this, but am I going to have to figure out how to use Syslinux for this to work or can I boot straight from an ISO with BCDW? Just a bit confused.
The only way BCDW can boot an iso image is if all files are contained in the boot sector so what you're trying to do won't work. Your old method should still work as long as the ghost exe is now placed on the cd instead of inside the floppy image and you map the cd drive to a static drive letter so it can be executed via autoexec.bat
I've got a 5.6 MB floppy image (created with WinImage) that I use that has ghost 11 on it. I ran into the same problem you did when the new ghost version came out. It uses the Universal TCP/IP Network Bootdisk (netbootdisk.com) which will also give you DOS network drivers for around 100 cards. I can shoot you a copy of the floppy image without ghost in it if you'd like. Just pm me.
QUOTE (DeTard @ Jul 8 2008, 04:32 PM)
Hey guys, I've been trying to figure out how to make a Multiboot plugin that will work for an ISO I've made, but so far I haven't ran into any examples of an MS-DOS image booted from ISO, they are all from floppy images. Now, before someone suggests I just make it into a floppy image, I will say that this is what I used to do - up until I got to Ghost 11.5 which has an EXE that is 2.2MB. That makes it basically impossible for me to include that EXE into an ISO in addition to all the network drivers I'm using.
My solution to this was to make an ISO that uses a bootable floppy image with all the network drivers I want and a boot menu (using the config.sys syntax for the menu) to pick what NIC I'm trying to boot for. MS-DOS would then boot, loading OAKCDROM.SYS and MSCDEX.EXE to use the CD-ROM drive where I placed GHOST.EXE. So a 1.44MB floppy image along side a 2.2MB EXE, and it's all working on a standalone ISO.
From what I've seen, you can directly boot from a floppy image, but when booting from an ISO you have to specify a kernel to use for Syslinux. Maybe I'm just thinking way too hard about this, but am I going to have to figure out how to use Syslinux for this to work or can I boot straight from an ISO with BCDW? Just a bit confused.
Any help would be greatly appreciated!
My solution to this was to make an ISO that uses a bootable floppy image with all the network drivers I want and a boot menu (using the config.sys syntax for the menu) to pick what NIC I'm trying to boot for. MS-DOS would then boot, loading OAKCDROM.SYS and MSCDEX.EXE to use the CD-ROM drive where I placed GHOST.EXE. So a 1.44MB floppy image along side a 2.2MB EXE, and it's all working on a standalone ISO.
From what I've seen, you can directly boot from a floppy image, but when booting from an ISO you have to specify a kernel to use for Syslinux. Maybe I'm just thinking way too hard about this, but am I going to have to figure out how to use Syslinux for this to work or can I boot straight from an ISO with BCDW? Just a bit confused.
Any help would be greatly appreciated!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.