Hello UBCD-Users and developers,
If I prepare my USB Stick with the ubcd2usb tools in the tools dir
I can boot this USB-Stick at my notebook (IBM ThinkPad p42)
but I got an error:
---snip---
- InitDisk
Invalid Opcode at 0003 0001 ...
---snap---
if I try to start a freeDOS image. When freeDOS tries to
initalize the Disks the error (Invalid Opcode...) occurs.
How do I get it run and fix this problem?
btw: I have to set the boot order priority (IBM ThinkPad p42) to
1: USB HDD
2: ... any other
in order to boot from USB-Stick.
It does not boot with "USB FDD" or "USB CD"
as the first item in the boot order priority.
Does anybody know why or how to fix this?
Or how to prepare the USB-Stick as an "USB FDD"
or "USB CD" if this is a problem of the "init disks" process
of freeDOS?
I also have problems to boot a selfmade "win98se" (dos 7.10)
Bootdisk. Memdisk seems to redirect some interupts
---snip---
[...]
INT 13 08: Success, count = 1, BPT = f000:8d99
old: int13 = f00066d0 int15 = f00066d5
new: int13 = 9e400008 int15 = 9e400376
Loading boot sector... booting...
---snap---
and then nothing happens...
... and I have to reboot
btw: the images are working fine if I burn them
to a CD and boot from this CD... It seems to be difficult
to boot an USB-Stick as a harddisk, isn't it?
Thomas
freeDOS boot failure (Init-Disk) and MS-DOS 7.1 boot failure
Moderators: Icecube, StopSpazzing
sounds like a memory management issue. I suggest you upgrade the freedos imageif I try to start a freeDOS image. When freeDOS tries to
initalize the Disks the error (Invalid Opcode...) occurs.
How do I get it run and fix this problem?
viewtopic.php?t=1422
Code: Select all
INT 13 08: Success, count = 1, BPT = f000:8d99
old: int13 = f00066d0 int15 = f00066d5
new: int13 = 9e400008 int15 = 9e400376
Loading boot sector... booting...
---snap---
and then nothing happens...
... and I have to reboot
uh-huhIt seems to be difficult to boot an USB-Stick as a harddisk, isn't it?
[quote]sounds like a memory management issue. I suggest you upgrade the freedos image
viewtopic.php?t=1422[/quote]
There is "only" one image "dosubcd.igz/fdubcd.img"
but it happens with the version 3.40 _and_ version 3.42
(if i boot from my usb-Stick as a usb-hdd)
[code]INT 13 08: Success, count = 1, BPT = f000:8d99
old: int13 = f00066d0 int15 = f00066d5
new: int13 = 9e400008 int15 = 9e400376
Loading boot sector... booting...
---snap---
and then nothing happens...
... and I have to reboot [/code]
[quote]What is the size of the image (1.44Mb or 2.88Mb)??[/quote]
It happens either with 1.44mb or 2.88mb images... :-(
Thomas
viewtopic.php?t=1422[/quote]
There is "only" one image "dosubcd.igz/fdubcd.img"
but it happens with the version 3.40 _and_ version 3.42
(if i boot from my usb-Stick as a usb-hdd)
[code]INT 13 08: Success, count = 1, BPT = f000:8d99
old: int13 = f00066d0 int15 = f00066d5
new: int13 = 9e400008 int15 = 9e400376
Loading boot sector... booting...
---snap---
and then nothing happens...
... and I have to reboot [/code]
[quote]What is the size of the image (1.44Mb or 2.88Mb)??[/quote]
It happens either with 1.44mb or 2.88mb images... :-(
Thomas
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
Try ubcd2usb in UBCD 5.0 beta and boot with USB HDD.
I encountered this before and it was due to the geometry made by makefatboot in UBCD V4.x.
I encountered this before and it was due to the geometry made by makefatboot in UBCD V4.x.