DOS ain't dead - Jemm v5.68 + 386SWAT in Qemu & VirtualBox

Japheth

Germany (South),
14.12.2007, 20:08

Jemm v5.68 + 386SWAT in Qemu & VirtualBox (Emulation)

Hello,

the 386SWAT debugger works with both Qemu and VirtualBox. However, it causes an immediate close of the VM if Jemm is loaded and a protected-mode application is launched. The bug is located in 386SWAT or Qemu/VBox, but since there is almost no chance that it will be fixed (soon) there is a workaround available in form of a slightly modified JemmEx:

JemmEmu.zip

The package also contains a modified VESA32.DLL which runs with VirtualBox. The one contained in HXRT v2.12 doesn't work.

---
MS-DOS forever!

Rugxulo

Usono,
14.12.2007, 20:17

@ Japheth

Jemm v5.68 + 386SWAT in Qemu & VirtualBox

Post reply

> The bug is located in 386SWAT or Qemu/VBox, but
> since there is almost no chance that it will be fixed (soon) there is a
> workaround available in form of a slightly modified JemmEx:
>
> JemmEmu.zip
>
> The package also contains a modified VESA32.DLL which runs with
> VirtualBox. The one contained in HXRT v2.12 doesn't work.

Maybe you should put it all in HXRT.ZIP under /UNSUPP/ (or at least in the latest HXRTD) ??

Japheth

Germany (South),
15.12.2007, 10:04

@ Rugxulo

Jemm v5.68 + 386SWAT in Qemu & VirtualBox

Post reply

> Maybe you should put it all in HXRT.ZIP under /UNSUPP/ (or at least in the
> latest HXRTD) ??

The VESA32.DLL binary will be part of next HXRT.

But why Jemm? It is not related to HX - and I have some doubts that there exists more than 1 person - me included - using Qemu/VBox+Jemm+386SWAT. It's just in case.

---
MS-DOS forever!

Rugxulo

Usono,
15.12.2007, 18:53

@ Japheth

Jemm v5.68 + 386SWAT in Qemu & VirtualBox

Post reply

> But why Jemm? It is not related to HX - and I have some doubts that there
> exists more than 1 person - me included - using Qemu/VBox+Jemm+386SWAT.
> It's just in case.

Do you recommend using other EMMs instead of JEMM with HX? Is not JEMM the best for it (over DR-DOS 7.03's or FreeDOS' old 2.26, at least)? Besides, it's small enough, and including a patched version in HXRT.ZIP would be easier than downloading separately. Just my $0.02.

Berlin, Germany,
15.12.2007, 21:21

@ Japheth

Jemm v5.68 + 386SWAT in Qemu & VirtualBox

Post reply

> application is launched. The bug is located in 386SWAT or Qemu/VBox, but
> since there is almost no chance that it will be fixed (soon) there is a

So you already wrote to Bob Smith about this issue? :-)

---
Forum admin

Japheth

Germany (South),
16.12.2007, 10:34

@ rr

Jemm v5.68 + 386SWAT in Qemu & VirtualBox

Post reply

> So you already wrote to Bob Smith about this issue? :-)

No - but it wouldn't make any difference. IIRC, in my last email conversation with Bob Smith about 2 years ago - he announced that he intends to make 386SWAT Open Source. I'm still waiting for this to happen.

---
MS-DOS forever!

jassenna Campinas,SP,Brazil, 20.12.2007, 04:14 @ Japheth	Jemm v5.68 + 386SWAT in Qemu & VirtualBox Post reply
	Did you ever use Jemmex with 386SWAT (No Qemu, no VirtualBox, no emulation- just DOS ) ? I tried it and could not make it work: if either is loaded, the other fails to load. May post the (fairly long) error messages here or send them directly to Japheth, if he is interested.

Japheth

Germany (South),
20.12.2007, 10:23

@ jassenna

Jemm + 386SWAT in true DOS

Post reply

> Did you ever use Jemmex with 386SWAT (No Qemu, no VirtualBox, no
> emulation- just DOS ) ?

Of course.

> I tried it and could not make it work: if either is loaded, the
> other fails to load.
> May post the (fairly long) error messages here or send them directly
> to Japheth, if he is interested.

I'm not sure if the error messages will help a lot. I used 386SWAT with JemmEx under MS-DOS 7.1 and FreeDOS without problems. But I always loaded JemmEx first and then 386SWAT in CONFIG.SYS:

DOS=HIGH,NOAUTO,UMB STACKS=0,0 FILESHIGH=80 LASTDRIVEHIGH=Z FCBSHIGH=4,0 BUFFERSHIGH=16 Country=049,850,C:\country.sys DEVICE=C:\UMBPCI.SYS /I=D000-DFFF DEVICE=C:\JEMMEX.EXE FRAME=E000 S=D000-DFFF FASTBOOT MIN=48 SPLIT DEVICEHIGH=C:\386SWAT.LOD PRO=C:\386SWAT.PRO DEVICEHIGH=C:\JLOAD.EXE -q C:\XDMA32.DLL /F DEVICEHIGH=C:\JLOAD.EXE -q C:\XCDROM32.DLL /D:CD001$ /F /32 DEVICEHIGH=C:\JLOAD.EXE -q C:\KEYBGR.DLL DEVICEHIGH=C:\HXLDR32.EXE -Q C:\DPMILD32.EXE INSTALLHIGH=C:\DOSKEY.COM INSTALL=C:\SHCDX33C.COM /Q /D:CD001$ /~ SHELL=C:\COMMAND.COM /P /E:512

However, if you've activated 386SWAT's "trapgenp" option, the debugger will stop at Jemm's "v86 breakpoints", which are implemented as HLT opcodes. So you most likely will have to modify your 386SWAT.PRO, note the "gpskip" line in the following excerpt:

; Recommended options are trapdiv ; Direct INT 00h to 386SWAT (Divide Overflow Fault) trapnmi ; Direct INT 02h to 386SWAT (Non-maskable interrupt) trapbound ; Direct INT 05h to 386SWAT (BOUND Fault) trapinv ; Direct INT 06h to 386SWAT (Invalid Opcode Fault) trapstack ; Direct INT 0Ch to 386SWAT (Stack Fault) trapgenp ; Direct INT 0Dh to 386SWAT (General Protection Fault) trappage ; Direct INT 0Eh to 386SWAT (Page Fault) x15 ; Pass through all INT 15h memory calls gpskip=hlt,ind,ini,ins,outd,outi,outs,crn ;

---
MS-DOS forever!