Menu
▾
▴
freedos-devel
|
From: Eric A. <e....@jp...> - 2024-08-15 22:14:12
|
Hi! I have been watching https://www.youtube.com/watch?v=K6-AlpCEqpc where Phils Computer Lab tests SBEMU with the pre-installed FreeDOS image which you can download from SBEMU's crazii. At one point, a game crashes with a loop of the following, some leading 0s omitted by me: JemmEx: exception 06 occured at CS:EIP=9689:FF14, ERRC=0 SS:ESP=D70A:C7D4 EBP=FFFF EFL=33093 CR0=80000013 CR4=200 EAX=FFFF9002 EBX=FFFF0007 ECX=FFFFFF00 EDX=FFFFF1EC ESI=40001A EDI=0EFF DS=0040 ES=FFFF FS=FFFF GS=00D9 [CS:IP]=FF FF FF FF FF FF FF FF Press ESC to abort program JemmEx: exception 06 occured at CS:EIP=9689:FF14, ERRC=0 SS:ESP=D70A:C7BE EBP=FFFF EFL=33093 CR0=80000013 CR4=200 EAX=FFFF9002 EBX=FFFF0007 ECX=FFFFFF00 EDX=FFFFF1EC ESI=40001A EDI=0EFF DS=0040 ES=FFFF FS=FFFF GS=00D9 [CS:IP]=FF FF FF FF FF FF FF FF Press ESC to abort program and so on, all registers except ESP stay constant and the video shows a loop of JemmEx messages scrolling through as the stack pointer goes down while CS:EIP is frozen pointing to an impossible FF FF opcode. Exc. 06 is undefined opcode. As the messages scroll so fast, I am not sure whether each instance actually shows all lines. The may even be nested? Later in the same video, F-117A mgraphic crashes, with far more readable JemmEx reactions: > JemmEx: exception 0C occured at CS:EIP=0360:2A01, ERRC=0 > SS:ESP=0360:FFEA EBP=0 EFL=33202 CRO=80000013 CR4=00000200 > EAX=0021 EBX=0 ECX=0 EDX=FFEC ESI=FFFF EDI=01FF > DS=0350 ES=0350 FS=0350 GS=O2BA [C3:IP]=36 8B 28 36 8B 88 B8 01 > Press ESC to abort progran > > JemmEx: exception 06 occured at CS:EIP=0000:0108, ERRC=0 > SS:ESP=0914:10002 EBP=C600 EFL=00033246 CRO=80000013 CR4=200 > EAX=0 EBX=0 ECX=0 EDX=0 ES1=0 EDI=0 > DS=0 ES=0 FS=0 GS=0 [C3:IP]=65 F0 00 F0 36 03 00 C0 > Press ESC to abort program > > JemmEx: exception 0D occured at CS:EIP=D79B:0984, ERRC=0 > SS:ESP=00D9:08D0 EBP=0 EFL=33093 CRO=80000013 CR4=200 > EAX=00FF EBX=0 ECX=FF54 EDX=0904 ESI=A8B1 EDI=0 > DS=00D9 ES=D7A0 FS=0 GS=0 [CS:IP]=67 66 2E 83 3C 9D 4C 04 ... This starts with a stack error first, "mov bp,[ss:bx+si]" wrapping the end of the first 64 kB of the stack segment, then an undefined opcode exception apparently caused by an invalid locked combination saying GS: LOCK: ADD AL,DH etc. and finally a general protection fault. Of course this does not tell much about whether it was futile to try to abort the program after the first stack exception, but note how there is no LOOP of exceptions here, so it gets a lot easier to read the messages :-) Thanks to https://www.sandpile.org/ for their tables :-) Likewise, the F-19 game also crashes, even with loadfix: JemmEx: exception 0D occured at CS:EIP=1025:4142, ERRC=0 SS:ESP:2025:DAC6 EBP=DAD0 EFL=33282 CR0=80000013 CR4=200 EAX=0 EBX=FFFE ECX=9BCC EDX=4605 ESI=C88C EDI=0 DS=2025 ES=46E8 FS=1015 GS=02BA [CS:IP]=89 47 01 89 7F 03 83 C6 which is mov [bx+1],ax and again wraps the end of some 64 kB boundary, but you actually get to read the text without a loop :-) *So now I wonder why JemmEx exception messages sometimes* *end up in a loop, while usually they do not, luckily.* The video features kernel 2043 (2021-05-14) FAT32 Watcom 386, JemmEx 5.84 02/11/23, QPIEMU, FreeCOM 0.85a 2021-07-10, UDVD2 (not used, no drive in the shown thin client), SBEMU (in VIA VT82XX AC97 mode), CuteMouse 2.1beta4, originally based on the FreeDOS 1.3 distro, it seems. It also mentions Aladdin failing to start, with the message "XMS allocation error.." (sic!) and Lotus 3 crashing with "Interrupt divide by zero, stack: D34C 0360 3002 518D ADE8 EB6F EB4A 314A E8D2 B117 C689 C389 7C80" In Sam+Max, audio setup fails with "hdpmi: fatal exit 0007". In Space Quest 5 adlib works, while emulated SB use hangs. Finally, some related GOOD news from this video: TETRIS CLASSIC is working fine :-) It is one of the games mentioned in my "game compatibility updates?" post as a game which was NOT working in 2022 :-) Cheers, Eric |
|
From: <je...@sh...> - 2024-08-16 10:19:25
|
Hi Eric, I was having similar issues. So, switched to VSBHDA. Afterwards, I was still experiencing lots of problems and submitted a bug report. But as it turned out, it was user error. I just needed to change the configuration settings and that fixed me right up. :-) > On Aug 15, 2024, at 6:13 PM, Eric Auer via Freedos-devel <fre...@li...> wrote: > > > Hi! I have been watching > > https://www.youtube.com/watch?v=K6-AlpCEqpc > > where Phils Computer Lab tests SBEMU with the pre-installed > FreeDOS image which you can download from SBEMU's crazii. > > At one point, a game crashes with a loop of the following, > some leading 0s omitted by me: > > JemmEx: exception 06 occured at CS:EIP=9689:FF14, ERRC=0 > SS:ESP=D70A:C7D4 EBP=FFFF EFL=33093 CR0=80000013 CR4=200 > EAX=FFFF9002 EBX=FFFF0007 ECX=FFFFFF00 EDX=FFFFF1EC > ESI=40001A EDI=0EFF > DS=0040 ES=FFFF FS=FFFF GS=00D9 [CS:IP]=FF FF FF FF FF FF FF FF > Press ESC to abort program > > JemmEx: exception 06 occured at CS:EIP=9689:FF14, ERRC=0 > SS:ESP=D70A:C7BE EBP=FFFF EFL=33093 CR0=80000013 CR4=200 > EAX=FFFF9002 EBX=FFFF0007 ECX=FFFFFF00 EDX=FFFFF1EC > ESI=40001A EDI=0EFF > DS=0040 ES=FFFF FS=FFFF GS=00D9 [CS:IP]=FF FF FF FF FF FF FF FF > Press ESC to abort program > > and so on, all registers except ESP stay constant and the > video shows a loop of JemmEx messages scrolling through as > the stack pointer goes down while CS:EIP is frozen pointing > to an impossible FF FF opcode. Exc. 06 is undefined opcode. > > As the messages scroll so fast, I am not sure whether each > instance actually shows all lines. The may even be nested? > > Later in the same video, F-117A mgraphic crashes, with far > more readable JemmEx reactions: > >> JemmEx: exception 0C occured at CS:EIP=0360:2A01, ERRC=0 >> SS:ESP=0360:FFEA EBP=0 EFL=33202 CRO=80000013 CR4=00000200 >> EAX=0021 EBX=0 ECX=0 EDX=FFEC ESI=FFFF EDI=01FF >> DS=0350 ES=0350 FS=0350 GS=O2BA [C3:IP]=36 8B 28 36 8B 88 B8 01 >> Press ESC to abort progran >> JemmEx: exception 06 occured at CS:EIP=0000:0108, ERRC=0 >> SS:ESP=0914:10002 EBP=C600 EFL=00033246 CRO=80000013 CR4=200 >> EAX=0 EBX=0 ECX=0 EDX=0 ES1=0 EDI=0 >> DS=0 ES=0 FS=0 GS=0 [C3:IP]=65 F0 00 F0 36 03 00 C0 >> Press ESC to abort program >> JemmEx: exception 0D occured at CS:EIP=D79B:0984, ERRC=0 >> SS:ESP=00D9:08D0 EBP=0 EFL=33093 CRO=80000013 CR4=200 >> EAX=00FF EBX=0 ECX=FF54 EDX=0904 ESI=A8B1 EDI=0 >> DS=00D9 ES=D7A0 FS=0 GS=0 [CS:IP]=67 66 2E 83 3C 9D 4C 04 > ... > > This starts with a stack error first, "mov bp,[ss:bx+si]" > wrapping the end of the first 64 kB of the stack segment, > then an undefined opcode exception apparently caused by an > invalid locked combination saying GS: LOCK: ADD AL,DH etc. > and finally a general protection fault. > > Of course this does not tell much about whether it was > futile to try to abort the program after the first stack > exception, but note how there is no LOOP of exceptions > here, so it gets a lot easier to read the messages :-) > > Thanks to https://www.sandpile.org/ for their tables :-) > > Likewise, the F-19 game also crashes, even with loadfix: > > JemmEx: exception 0D occured at CS:EIP=1025:4142, ERRC=0 > SS:ESP:2025:DAC6 EBP=DAD0 EFL=33282 CR0=80000013 CR4=200 > EAX=0 EBX=FFFE ECX=9BCC EDX=4605 ESI=C88C EDI=0 > DS=2025 ES=46E8 FS=1015 GS=02BA [CS:IP]=89 47 01 89 7F 03 83 C6 > > which is mov [bx+1],ax and again wraps the end of some > 64 kB boundary, but you actually get to read the text > without a loop :-) > > *So now I wonder why JemmEx exception messages sometimes* > *end up in a loop, while usually they do not, luckily.* > > The video features kernel 2043 (2021-05-14) FAT32 Watcom 386, > JemmEx 5.84 02/11/23, QPIEMU, FreeCOM 0.85a 2021-07-10, > UDVD2 (not used, no drive in the shown thin client), > SBEMU (in VIA VT82XX AC97 mode), CuteMouse 2.1beta4, > originally based on the FreeDOS 1.3 distro, it seems. > > It also mentions Aladdin failing to start, with the > message "XMS allocation error.." (sic!) and Lotus 3 > crashing with "Interrupt divide by zero, stack: > D34C 0360 3002 518D ADE8 EB6F EB4A 314A > E8D2 B117 C689 C389 7C80" > > In Sam+Max, audio setup fails with "hdpmi: fatal exit 0007". > In Space Quest 5 adlib works, while emulated SB use hangs. > > Finally, some related GOOD news from this > video: TETRIS CLASSIC is working fine :-) > > It is one of the games mentioned in my > "game compatibility updates?" post as a > game which was NOT working in 2022 :-) > > Cheers, Eric > > > > _______________________________________________ > Freedos-devel mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freedos-devel |
|
From: Eric A. <e....@jp...> - 2024-08-16 13:48:27
|
Hi Jerome, please be more specific, which games crashed with sbemu for you, on which hardware and with which configuration, with which jemmex error messages? And which configuration of vsbhda made which of the games work and which are still not working? Maybe you could even share the insight with Phil's Computer Lab? Thank you :-) Good to know that you got (most?) things to work :-) Eric > Hi Eric, > > I was having similar issues. So, switched to VSBHDA. Afterwards, I > was still experiencing lots of problems and submitted a bug report. > But as it turned out, it was user error. I just needed to change > the configuration settings and that fixed me right up. > > :-) > >> On Aug 15, 2024, at 6:13 PM, Eric Auer via Freedos-devel <fre...@li...> wrote: >> >> >> Hi! I have been watching >> >> https://www.youtube.com/watch?v=K6-AlpCEqpc >> >> where Phils Computer Lab tests SBEMU with the pre-installed >> FreeDOS image which you can download from SBEMU's crazii... |
|
From: Jerome S. <je...@sh...> - 2024-08-16 20:24:17
|
Hi Eric, > On Aug 16, 2024, at 9:48 AM, Eric Auer via Freedos-devel <fre...@li...> wrote: > > > Hi Jerome, > > please be more specific, which games crashed with sbemu for you, I honestly don’t recall. I only did a very little testing on one of my machines. I don’t even remember if it was the P4 or Atom. I was very busy at the time and it was sort-of working. I decided to try again later. When later arrived, I was aware of the VSBHDA fork. Which to my understanding of the documentation, works better with JEMM. So, I decided to try to get that working instead. > on which hardware and with which configuration, with which jemmex > error messages? Initial issues were no sound in some games. Random computer freezing and strangely frequent JEMM exceptions while just using the command line. Most of my testing was in two games. SaysWho and FreeDOM. SaysWho is that simple memory game I made. In part, it was to test the audio driver for my gaming engine. The game will use the PC speaker for sound. However, if an Adlib compatible sound card is present it will use that for audio. As you know, all those old SB cards and many others are Adlib compatible. That game would run and there would be no sound at all. Which meant it saw it was compatible with Adlib, but no sound came out of it. FreeDOM had sound. But, would freeze after a little while. > And which configuration of vsbhda made which of > the games work and which are still not working? Changing the BLASTER environment variable setting for the IRQ fixed it. I think using IRQ 2 instead of the more common default value was the solution. Both of those games now work without issue. I also recommend setting the emulator volume to max when loading it. If not specified, it can be very quiet. Without that setting, when testing on the ACER Netbook, it was barely audible at all. > Maybe you could even share the insight with Phil's Computer Lab? > > Thank you :-) Good to know that you got (most?) things to work :-) Yup, mostly working very well. Since I don’t play games often and to insure there are no conflicts when running the emulator, I don’t have either of the machines that need it for sound boot with the emulator running. If need be, I’ll can just run it later as needed for games. The ACER netbook has very small speakers and is barely worth having sound. The Toshiba P4 is a battleship sized laptop. Or, more accurately a desktop substitute. The audio from it is loud when the emulator running. My 486 notebook does not have a sound card in its docking station at present. My Pentium Pro has an SB AWE64 Gold and does not need the emulator. > Eric :-) Jerome > > >> Hi Eric, >> I was having similar issues. So, switched to VSBHDA. Afterwards, I >> was still experiencing lots of problems and submitted a bug report. >> But as it turned out, it was user error. I just needed to change >> the configuration settings and that fixed me right up. >> :-) >>>> On Aug 15, 2024, at 6:13 PM, Eric Auer via Freedos-devel <fre...@li...> wrote: >>> >>> >>> Hi! I have been watching >>> >>> https://www.youtube.com/watch?v=K6-AlpCEqpc >>> >>> where Phils Computer Lab tests SBEMU with the pre-installed >>> FreeDOS image which you can download from SBEMU's crazii... > > > > > > _______________________________________________ > Freedos-devel mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freedos-devel |
|
From: tom e. <te...@dr...> - 2024-08-16 14:33:46
|
Hallo Herr Jerome Shidel via Freedos-devel, am Freitag, 16. August 2024 um 12:19 schrieben Sie: > Hi Eric, > I was having similar issues. So, switched to VSBHDA. Afterwards, I was still experiencing lots of problems and submitted a bug report. But as it turned out, it was user error. I just needed to change the configuration settings and that fixed me right up. Now it would be cool if you shared the working configuration and the reason the configuration before filed. "I managed to find a solution" mails without presenting the solution is bragging and wasting everybody's time. Tom |
|
From: Jerome S. <je...@sh...> - 2024-08-16 20:33:23
|
Hi Tommy, > On Aug 16, 2024, at 10:34 AM, tom ehlert via Freedos-devel <fre...@li...> wrote: > > Hallo Herr Jerome Shidel via Freedos-devel, > > am Freitag, 16. August 2024 um 12:19 schrieben Sie: > >> Hi Eric, > >> I was having similar issues. So, switched to VSBHDA. Afterwards, I was still experiencing lots of problems and submitted a bug report. But as it turned out, it was user error. I just needed to change the configuration settings and that fixed me right up. > > Now it would be cool if you shared the working configuration and the reason the configuration before filed. I’m not at my machine at present. But, later I will try to remember to do that. > "I managed to find a solution" mails without presenting the solution is bragging and wasting everybody's time. Nah, it is worse than that. I didn’t find a solution. I submitted an issue and begged Japheth for help. He was kind enough to tell me what to do. > Tom > :-) Jerome > > > _______________________________________________ > Freedos-devel mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freedos-devel |
|
From: <je...@sh...> - 2024-08-16 22:08:24
|
Hi Tom, > On Aug 16, 2024, at 10:33 AM, tom ehlert via Freedos-devel <fre...@li...> wrote: > > Hallo Herr Jerome Shidel via Freedos-devel, > > am Freitag, 16. August 2024 um 12:19 schrieben Sie: > >> Hi Eric, > >> I was having similar issues. So, switched to VSBHDA. Afterwards, I was still experiencing lots of problems and submitted a bug report. But as it turned out, it was user error. I just needed to change the configuration settings and that fixed me right up. > > Now it would be cool if you shared the working configuration and the reason the configuration before filed. > > "I managed to find a solution" mails without presenting the solution is bragging and wasting everybody's time. > > Tom VSBHDA comes with a couple example startup batch files. I only use the one called START.BAT. Originally, it contained the following lines: @echo off rem run vsbhda jload -q qpiemu.dll jload -q jhdpmi.dll lh hdpmi32i -x2 rem set blaster=A220 I7 D1 T3 rem set blaster=A220 I7 D1 T4 set blaster=A220 I7 D1 H5 T6 vsbhda After Japheth told me what I should try, I simply changed that file to the following: @echo off rem run vsbhda jload -q qpiemu.dll jload -q jhdpmi.dll lh hdpmi32i -x2 rem set blaster=A220 I7 D1 T3 rem set blaster=A220 I7 D1 T4 rem set blaster=A220 I7 D1 H5 T6 set blaster=A220 I2 D1 H5 T6 vsbhda /VOL9 And for me at least, it fixed the crashing on both the Acer Aspireone D250-1924 and the Toshiba Satellite P25-S5092. Even though I was getting JEMM exceptions, my problem was most likely caused by an IRQ conflict. Jerome |
Thanks for helping keep SourceForge clean.
X