Now, getting a CPU exception (fwd)

Now, getting a CPU exception (fwd)

[James B. Hiller]

Ref my previous email of a few minutes ago:  a couple other factoids:

a.  Am using command.com, io.sys, msdos.sys from Win95

b.  The issue seems to NOT happen when I start from my old hdimage and
lredir c: to /dosc from there.

c.  The tail end of this huge boot log contains:

MFS: Entering dos_fs_redirect, FN=22
MFS: selecting drive fn=22 sda_cds=0x2d80
MFS: selected drive 2: /dosc/
MFS: Process terminated PSP=65535
MFS: hlist_pop_psp: PSP=65535
MFS: Finished dos_fs_redirect
int 0x2f, ax=0x1122
Do INT0x21: Using caller_function()
INT21 (0) at f433:3c5f: AX=6201, BX=392f, CX=0000, DX=886a, DS=0426, ES=f433
int 0x21, ax=0x6201
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
1 < 5
DMA: Wrote 0x5 into Channel 0 Length (Byte 0)
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
MOUSE: Skipping irq, mask=0x0, ev=0x0, cs=0x0, ip=0x0
Doing REP outsw(0xcc0f) 1 words at 0x50, DF 0
PORTw: cc0f not available for write
cc0f { 140
DMA: Unhandled Read on 0x000f
f > ff
Doing REP outsw(0xcc0f) 1 words at 0x52, DF 0
PORTw: cc0f not available for write
cc0f { f000
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
Doing REP outsw(0xcc0f) 1 words at 0x54, DF 0
PORTw: cc0f not available for write
cc0f { 3f6
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
SIGILL while in vm86()
ERROR: LOCK prefix not permitted!
Return for SIGNAL
SIGILL while in vm86()

and after a bunch more these, finishes with the exception as
shown in the previous mail:

> ERROR: unexpected CPU exception 0x06 err=0x00000000 cr2=000b88c2 while in vm86 (DOS)
> Program=sigsegv.c, Line=162
> EIP: 0000:0000992b ESP: 0000:00004608  VFLAGS(b): 00000 01110000 10000011
> EAX: 5803a103 EBX: 00008e0b ECX: 0000415e EDX: 0044ffff VFLAGS(h): 00007083
> ESI: 00000050 EDI: 00000b00 EBP: 0000b17f DS: 0000 ES: 0005 FS: 0000 GS: 0000
> FLAGS: CF SF IF NT RF VM  IOPL: 3
> STACK: 00 00 00 00 00 26 04 a1 01 26 -> 04 00 00 00 00 01 eb 05 43 3a 
> OPS  : 00 9e e1 00 99 02 00 9e e1 00 -> 63 d7 d8 e1 00 89 97 01 7c 00 
>         63d7                0000:992b arpl    di,dx
> 
> Aborted

thx,
jbh

Re: Now, getting a CPU exception (fwd)

[norseman]

"James B. Hiller" wrote:
> 
> Ref my previous email of a few minutes ago:  a couple other factoids:
> 
> a.  Am using command.com, io.sys, msdos.sys from Win95
> 

===============================

In a movie called BIG RED ONE, the private comes upon a bad guy in the
ovens of a disposal camp and keeps emptying his rifle into the bad guy.
Lee Marvin approaches, slips in a fresh clip into the privates rifle 
and wispers into the private's ear      "I think you got him" .

Let me whisper in your ear:
             ALL WINDOWS "MSDOS" stuff is NOT MSDOS!!! 

WINDOWS "DOS" is a kind of emulator that requires MS-Windows be running.
The proof is by trying to run a regular MSDOS protected mode program. 
(It won't run under an emulator.)


Steven L. Turner  LLS                      stevet@water.ca.gov
GIS Tech. Support                          (916) 653-4041 V/M
Unit    - Land & Water Use                 (no fax number at this time)
Section - Statewide Planning
Division of Planning and Local Assistance
Department of Water Resources
State of California
901 "P Street, Rm 200A
Sacramento, CA  95814

Re: Now, getting a CPU exception (fwd)

[Jan Willem Stumpel]

norseman wrote:

> WINDOWS "DOS" is a kind of emulator that requires MS-Windows be
> running. The proof is by trying to run a regular MSDOS
> protected mode program. (It won't run under an emulator.)

Rubbish. MS-DOS from Win95 and Win98 is perfectly OK with dosemu.

If you have Windows 98 (or 95) you can make a bootable floppy,
under Windows in DOS mode, with the sys a: command, and copy the
three files from the floppy (ignore drvspace.bin which is also there).

The DOS utilities belonging to Windows 95/98 are in
c:\windows\command. Copy them to your DOS (=dosemu) path.

NOTE: To boot the DOS from Win98/95 neatly (without a Windows logo
flashing by, and arriving at the correct prompt) it is best to
edit msdos.sys. In 'Windows DOS' this is a text file, which
originally has just one line in it:

;SYS

You should edit it (with an MS-DOS editor, or for instance with
joe -crlf) to read

[Options]
Logo=0
;SYS

Good luck, Jan

Re: Now, getting a CPU exception (fwd)

[James B. Hiller]

Hi.

> > Ref my previous email of a few minutes ago:  a couple other factoids:
> > 
> > a.  Am using command.com, io.sys, msdos.sys from Win95

[snip simile]

Nice simile :-)

> Let me whisper in your ear:
>              ALL WINDOWS "MSDOS" stuff is NOT MSDOS!!! 

Understood.  But I was always under the impression that the DOS
environment from Win95 was still "whole", and that it's not unless
you're in the NT/2000 domain that what you explain is an issue.

And, aside from that, been using this componentry with DOSEMU
(albeit only from an hdimage perspective) since like 1996.
> 
> WINDOWS "DOS" is a kind of emulator that requires MS-Windows be running.
> The proof is by trying to run a regular MSDOS protected mode program. 
> (It won't run under an emulator.)

If this is an issue here, methinks Mr Oldeman may have commented
thusly already?

But I do have MS-DOS 6.22 disks around if needs be.

jbh

Re: Now, getting a CPU exception (fwd)

[Justin Zygmont]

On Mon, 19 Jan 2004, James B. Hiller wrote:

> Hi.
> 
> > > Ref my previous email of a few minutes ago:  a couple other factoids:
> > > 
> > > a.  Am using command.com, io.sys, msdos.sys from Win95
> 
> [snip simile]
> 
> Nice simile :-)
> 
> > Let me whisper in your ear:
> >              ALL WINDOWS "MSDOS" stuff is NOT MSDOS!!! 
> 
> Understood.  But I was always under the impression that the DOS
> environment from Win95 was still "whole", and that it's not unless
> you're in the NT/2000 domain that what you explain is an issue.
> 
> And, aside from that, been using this componentry with DOSEMU
> (albeit only from an hdimage perspective) since like 1996.
> > 
> > WINDOWS "DOS" is a kind of emulator that requires MS-Windows be running.
> > The proof is by trying to run a regular MSDOS protected mode program. 
> > (It won't run under an emulator.)
> 
> If this is an issue here, methinks Mr Oldeman may have commented
> thusly already?
> 
> But I do have MS-DOS 6.22 disks around if needs be.

I also have a binary download of dosemu 1.2 with msdos 6.22 if need be.  
ftp://solarflow.dyndns.org/pub

Re: Now, getting a CPU exception (fwd)

[norseman]

Jan Willem Stumpel wrote:
> 
> norseman wrote:
> 
> > WINDOWS "DOS" is a kind of emulator that requires MS-Windows be
> > running. The proof is by trying to run a regular MSDOS
> > protected mode program. (It won't run under an emulator.)
> 
> Rubbish. MS-DOS from Win95 and Win98 is perfectly OK with dosemu.
> 
> If you have Windows 98 (or 95) you can make a bootable floppy,
> under Windows in DOS mode, with the sys a: command, and copy the
> three files from the floppy (ignore drvspace.bin which is also there).
> 

Jan is right - this does work. (My WIN-98SE shows dos ver.4.10.2222)

> The DOS utilities belonging to Windows 95/98 are in
> c:\windows\command. Copy them to your DOS (=dosemu) path.
> 

after you boot DOSEMU, do a mem/c/p and see if WIN appears in memory.
does on my test. (It's the link to windows so's it can work.)


> NOTE: To boot the DOS from Win98/95 neatly (without a Windows logo
> flashing by, and arriving at the correct prompt) it is best to
> edit msdos.sys. In 'Windows DOS' this is a text file, which
> originally has just one line in it:
> 
> ;SYS
>

assumes you are in Windows. If in WIN-dos boot then .sys is the
regular binary application/system calls section. Windows swaps
contents dependant on boot.

 
> You should edit it (with an MS-DOS editor, or for instance with
> joe -crlf) to read
> 
> [Options]
> Logo=0
> ;SYS
> 
> Good luck, Jan
> 
=================
I learned something. Thank you Jan.


Steve Turner
norseman@firstlight.net