No support for DOS 3.3 and earlier?
Brought to you by:
bartoldeman
Menu
▾
▴
#36 No support for DOS 3.3 and earlier?
I have MSDOS 6.22, 5.0 and 4.0 all working fine,
however, I hit a "wall" when I moved on to 3.3, that
exibits the same issues be it MS 3.3, PC 3.3 or MS 3.2.
I has expected "smooth sailing" until I went to tackle
3.0, as 3.0 wasn't desiged to know what a "network" is!
No error messages are output, looks just like this:
[wayne@daytona ~]$ dosemu
[wayne@daytona ~]$
One line in the bootlog is all that says anything.
The error message from boot.log:
SIGILL while in vm86()
ERROR: unexpected CPU exception 0x06 err=0x00000000
cr2=00000000 while in vm86 (DOS)
I will be tackling this one myself, however, if someone
"just happens to have" a good idea of where I should
look - that's what I came here for -- In the meanwhile,
I'll start from the other end - MS 2.11 and, PC DOS 1.1
from my original bootdisk from 23 years ago!
Btw: I don't run it on the system console, only place I
don't in fact. After closely integrating DOSEmu, PuTTY,
DOS 6.22 and a vertcal-market DOS app a client of mine
had >$20,000 invested in, I got this wild idea.....
I've been known to grant access to it for those who
ask, giving them an http://URL(!).
Logged In: YES
user_id=1240853
MS DOS 2.11 dumps similarly, but a lot more artifacts were
left in the errorlog!:
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
SIGILL while in vm86()
ERROR: unexpected CPU exception 0x06 err=0x00000000
cr2=00000000 while in vm86 (DOS)
leavedos(4|0x4) called - shutting down
leavedos() called from within a signal context!
Logged In: YES
user_id=501371
You should try booting from the hdimage instead of a directory.
The boot secrot that dosemu generates for booting from a
directory, doesn't seem to work for such an old DOS.
This is not even a bug btw. Support for booting MS-DOS 3.3
from a directory can probably be added (after all the redirector
support should already be there in that version of DOS), but
it is a feature request.
Moving to Feature Requests.
Logged In: YES
user_id=501371
Logged In: YES
user_id=1240853
I've been using Dosemu to tinker with stuff for two years or
so, and never used an hdimage for anything -- I'll soon try
to get around to tinkering "on", rather than "on something
else while using" -- where I'm going with this, should
eventually make me rather inimite with int 13H code, et.al.
Even though 3.1, 3.2, and 3.3 do have the rediretor
support (3.1 debuted ofically to support it), save any
effort at making them work, as images will be used
anyway.... Save it to hold your breath when my brain breaks
the wind while getting MS Client 3.0 to operate the way I'd
like to see it.... Thx!