's Avatar

@joncampbell123.bsky.social

2 Followers  |  2 Following  |  13 Posts  |  Joined: 17.11.2024  |  1.6385

Latest posts by joncampbell123.bsky.social on Bluesky


Latest build soon to complete tonight should fix some issues to improve emulating your program in DOSBox-X.

23.01.2025 00:01 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 1    ๐Ÿ“Œ 0
Preview
CWSDPMI r7ใฎPC-98ๅฏพๅฟœ็Šถๆณใ‚’ใ™ใ“ใ—ๆ”นๅ–„ใ™ใ‚‹ใƒ‘ใƒƒใƒ CWSDPMI r7ใฎPC-98ๅฏพๅฟœ็Šถๆณใ‚’ใ™ใ“ใ—ๆ”นๅ–„ใ™ใ‚‹ใƒ‘ใƒƒใƒ. GitHub Gist: instantly share code, notes, and snippets.

There exists a version of CWSDPMI patched for PC-98 systems, can you try this in DOSBox-X and see if it works? It works for me, at least.

gist.github.com/lpproj/d4220...

22.01.2025 20:07 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 1    ๐Ÿ“Œ 0

What DOS extender is the real PC-9821 system using?

22.01.2025 16:22 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 1    ๐Ÿ“Œ 0

CWSDPMI is writing to ports 20h and 21h to set up the interrupt controller as if talking to IBM PC hardware, which doesn't work on PC-98 where those I/O ports are at 00h and 02h instead.

22.01.2025 16:21 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 1    ๐Ÿ“Œ 0

Notice that when your program actually does run, you can crash it right away with that error by pressing a key on the keyboard.

Can you try your program with a PC-98 aware version of CWSDPMI instead?

22.01.2025 16:02 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 1    ๐Ÿ“Œ 0

It's using CWSDPMI.EXE.

CWSDPMI isn't redirecting the IRQ interrupt vectors, which means while running there is a conflict between IRQ 0-7 and the protected mode exceptions.

"Coprocessor Overrun" means the extender saw INT 9h happen.

INT 9h is also the keyboard interrupt.

22.01.2025 16:02 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 1    ๐Ÿ“Œ 0

DOSBox-X should probably not include those on the Z: drive in PC-98 mode for that reason, and should include instead PC-98 versions of those where available.

22.01.2025 15:52 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 1    ๐Ÿ“Œ 0

Part of the problem is that those DOS extenders are IBM PC versions. They happen to work on PC-98 except that the code to print exception information on screen doesn't work and often hangs on PC-98.

22.01.2025 15:51 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 1    ๐Ÿ“Œ 0

DOSBox-X by default provides CWSDPMI, DOS4GW, and DOS32A. Which one is it running? Try running DOSBox-X with the --debug command line option and open the console, then run the game. It should say what files were opened and which one of the DOS extenders was involved.

22.01.2025 15:26 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 1    ๐Ÿ“Œ 0

What DOS extender are you using?

Is it a version designed for PC-98 systems?

22.01.2025 03:00 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 1    ๐Ÿ“Œ 0

DOSBox-X developer here. DOSBox-X has a PC-98 emulation mode, does it work there?

21.01.2025 16:40 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 1    ๐Ÿ“Œ 0

Better yet, find a Linux box and plug it in there. There's no autorun in Linux.

Of course worst case scenario, it could be one of those USB killer sticks...

28.11.2024 03:31 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 0    ๐Ÿ“Œ 0

Would it have anything to do with social media in the last 8 years? Or perhaps streaming services?

26.11.2024 09:27 โ€” ๐Ÿ‘ 0    ๐Ÿ” 0    ๐Ÿ’ฌ 0    ๐Ÿ“Œ 0

Life tip: Nobody is stopping you from putting a dot on the top of your USB cables

It takes 1 second and saves you trying both sides and somehow only plugging it in right when you look at it

16.11.2024 14:53 โ€” ๐Ÿ‘ 3542    ๐Ÿ” 242    ๐Ÿ’ฌ 214    ๐Ÿ“Œ 51

@joncampbell123 is following 2 prominent accounts