Page 3 of 4
Posted: Wed Jun 27, 2007 2:07 pm
by ertrules22
no, it says boot: a
Posted: Wed Jun 27, 2007 2:10 pm
by t0xic
I don't know. Here is my bochsrc:
Code: Select all
# You many now use double quotes around pathnames, in case
# your pathname includes spaces.
romimage: file=BIOS-bochs-latest, address=0xf0000
vgaromimage: VGABIOS-elpin-2.40
megs: 32
floppya: 1_44=phoenix-os-onyx.img, status=inserted
#floppya: 1_44=simple.bin, status=inserted
#ata0-master: type=cdrom, path=hd.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="hd.img", mode=flat, cylinders=4, heads=16, spt=63
boot: floppy
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 300000
keyboard_serial_delay: 250
keyboard_paste_delay: 100000
floppy_command_delay: 500
ips: 1000000
mouse: enabled=0
private_colormap: enabled=0
fullscreen: enabled=0
screenmode: name="sample"
keyboard_mapping: enabled=0, map=
ne2k: ioaddr=0x300, irq=3, mac=b0:c4:20:00:00:00
#keyboard_type: at
Make sure your's looks somthing like that
--Michael
Posted: Wed Jun 27, 2007 2:12 pm
by ertrules22
here is mine
note: mine came with do0rs, but looks similar to yours (except the top comments, check it out)
Code: Select all
# Bochs config for DoOrS-0.2.5-SR
romimage: file=BIOS-bochs-latest, address=0xf0000
vgaromimage: VGABIOS-elpin-2.40
megs: 32
floppya: 1_44=do0rs.img, status=inserted
boot: a
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 300000
keyboard_serial_delay: 250
keyboard_paste_delay: 100000
floppy_command_delay: 500
ips: 1000000
mouse: enabled=0
private_colormap: enabled=0
fullscreen: enabled=0
screenmode: name="DoOrS"
[/code]
Posted: Wed Jun 27, 2007 2:13 pm
by ertrules22
ohhh... perhaps it is missing the stuff at the bottom?
Posted: Wed Jun 27, 2007 2:16 pm
by t0xic
Try changing boot: a in your config file to boot: floppy, see if that helps
--Michael
Posted: Wed Jun 27, 2007 2:17 pm
by ertrules22
nope, it just came up with the same exact error
Posted: Wed Jun 27, 2007 2:19 pm
by t0xic
If you happen to have a hex editor (if you don't just google HxD), open up the image and make that the last two bytes of the first sector are 0x55 and 0xAA.
--Michael
Posted: Wed Jun 27, 2007 2:28 pm
by ertrules22
sorry, kinda new to this, I have HxD open, with the do0rs .img file open in it, but where do I look from there (sorry if I sound dumb, but remember that I have never done this before!) I can do a lot of stuff with computers, but osdev is new, so I'm just trying to get a hang of things!
Thanks,
ertrules22
Posted: Wed Jun 27, 2007 2:43 pm
by t0xic
I forgive you, we were all at that stage once
If you go to Extras->Open Disk Image, you will see the sectors cut out, and look at the last two characters in hex.
Or find offset 1F0, and go to bytes E and F, and tell me what they are. If the OS uses grub, you don't need to do this step, as it just makes sure the bootloader will actually run.
Posted: Wed Jun 27, 2007 2:51 pm
by ertrules22
okay on offset 1F0 0E is 55 0F is AA
Posted: Wed Jun 27, 2007 3:20 pm
by t0xic
Sorry for the late response:
I really don't know what the problem is... where can I download the floppy image, I'll see if I can troubleshoot it then.
--Michael
Posted: Thu Jun 28, 2007 11:13 am
by ertrules22
The link for do0rs OS is here:
http://www.mif.vu.lt/~anba1548/DoOrS/
Sorry for the late response:
It's okay, thanks for all the help, and I've even learned some stuff!
Posted: Thu Jun 28, 2007 11:19 am
by t0xic
DoOrS Won't run for me either
It's probably their fault
--Michael
Posted: Thu Jun 28, 2007 3:28 pm
by ertrules22
Well, that makes me feel better too! Oh well, I will try something else later, thanks all of your help!
what
Posted: Fri Jun 29, 2007 8:51 pm
by com1
why do we always get off subject in threads like this?