|
|
| Post Number: 11
|
xoben 
Group: Super Administrators
Posts: 849
Joined: Nov. 2003
|
 |
Posted on: Dec. 11 2003,10:01 |
|
   |
lower case problem ... it's ok now.
|
 |
|
|
| Post Number: 12
|
peter
Unregistered
|
|
Posted on: Dec. 11 2003,12:34 |
|
 |
sorry, but i think i'm to stupid to create the image. I'ld like to build a 4320KB large floppy image.
1.) I select my downloaded "boot_msd.img" as "seed image"
2.) I select 4320KB Image Size
3.) I select the Image Output Filename ("c:\4320.img")
4.) I open the new Image with WinImage V6.10.6100 but the image is empty and i'm not able to put some files into.
5.) If i download the 4320KB floppy image from your website, i'm able to edit this file with WinImage but after i delete all files from the image and insert "command.com", "io.sys" and "msdos.sys", the image doesn't boot anymore.
Okay, i know the wrong way - but what's the exact right way???
|
|
|
|
| Post Number: 13
|
peter
Unregistered
|
|
Posted on: Dec. 11 2003,12:40 |
|
|
After i closed EZB i can open the above created file "c:\4320.img" with WinImage, but the file is empty and if i put "io.sys" etc. into it, it still doesn't boot.
sorry for this, but EZB wasn't closed when i wrote the above message.
|
|
|
|
| Post Number: 14
|
martinx
Group: Members
Posts: 88
Joined: Nov. 2003
|
|
Posted on: Dec. 11 2003,20:28 |
|
|
Some files of MS-DOS 6.22 is position sensitive, please do as following:
1) Click 'Tools' and select 'Create New Image' on the popup menu, a dialoge window will appear
2) Set "boot_msd.img" as "seed image", select 4320KB for "Image Size(KB)", and specify "Image Output Filename" to "c:\easyboot\disk1\ezboot\4320.img", then click 'Create'
3) Make a temporary folder such as 'c:\temp', open 'boot_msd.img' by WinImage or UltraISO, and extract all files to 'c:\temp'
4) Open newly created '4320.img' by WinImage, firstly add 'c:\temp\io.sys', 'c:\temp\msdos.sys' next, 'c:\temp\command.com' and 'c:\temp\drvspace.bin' follows up - ONE BY ONE. Other files can be added as you need.
Then, you get it.
|
|
|
|
| Post Number: 15
|
teufel
Unregistered
|
|
Posted on: Dec. 12 2003,01:59 |
|
|
I created a 5.76 mb image with EasyBoot 4.55 beta, with the windows 2000 setup disk set (4 floppy set). I used the first diskette image as the seed image, and and added all filed from the disk set into the 5.76 image. Everything was created successfully, i boot the cd, select the 5.76 win2k image, and the image starts to load. Eventually i get a blue screen with a stop error "INACCESSABLE_BOOT_DEVICE" ive also seen similar errors with Partition Magic, after booting it cant read drive A:. Any help would be appreciated!
|
|
|
|
| Post Number: 16
|
martinx
Group: Members
Posts: 88
Joined: Nov. 2003
|
|
Posted on: Dec. 12 2003,04:15 |
|
|
For windows 2000 bootable CD, you can use w2ksect.bin and prepare files in non-emulation mode - just see above information on top of this topic.
|
|
|
|
| Post Number: 17
|
rattkin
Unregistered
|
|
Posted on: Dec. 12 2003,13:56 |
|
|
got same problem as teufel has. done exactly the same routine (4 disks, first as seed), but chosen 11mb image.
INACCESSABLE_BOOT_DEVICE still appears.
i know I CAN use bin file and start with no-emulation, but what i should do when i WANT to boot it this way. then if i cannot - why?
|
|
|
|
| Post Number: 18
|
teufel
Unregistered
|
|
Posted on: Dec. 12 2003,18:37 |
|
|
Im not looking for a "well, just put it on a cd then" awnser. Im telling you that the system has a problem accessing the image, my guess, since the image begins to load, is that the system has a problem accessing the image over 1.44/2.88mb? Is there a driver for the oversized floppy dirive emulator, that needs to be loaded maybe?
|
|
|
|
| Post Number: 19
|
martinx
Group: Members
Posts: 88
Joined: Nov. 2003
|
|
Posted on: Dec. 13 2003,08:45 |
|
|
You may be right. EasyBoot does not care anything about the boot loader of windows 2000, it just emulate the image, load MBR and transfer control to it.
|
|
|
|
| Post Number: 20
|
rattkin
Unregistered
|
|
Posted on: Dec. 13 2003,11:28 |
|
|
1. accesing bootimage over 1.44 : don't think it's a problem, cause win2k needs all four disks to start - when you're booting it from floppies, it reads first. then ask for second and yadayada...
when you merge 4 disks into one bigger image, and boot it with ezboot, all the files are loaded properly (means that win2k installer recognizes 4 disks and load files from all).
if it was a problem with acessing data over 1.44 it would probably ask for next disk or something (my guess only).
2. as far as i am concerned, win2k makes a ramdisk 'in background' and copy there files from floppies. so the startup runs from ramdisk and not from floppies directly.
3. then again it may be a problem with proper floppy emulation problem. for example i made few one-floppy linux bootdisks and tried to boot them via ezboot - image started, but then linux kernel is trying to mount filesystem in /dev/fd0  (not in virtual floppy). but i don't think there's a solution for that - it's hardcoded into a linux...
4. i've been told that inacessible boot device problem occurs when you're trying to boot from udma/66 disk. it's silly, but i wonder what will happen when i boot my comp directly from win2k floppies.  ))
5. doh' ! waiting for answers...
|
|
|
|
|
|
|
