NO$PSX V2.1 Released (20th Aug 2022)

[nocash]

Anybody tried the above test version? I'd really like to get that problem sorted out!

[Shadow]

All I get is

Code: Select all

debug
tv
fonts
b
bb

and then it closes the debugger, but I still need to kill it via task manager because it's secretly still running.

[null]

Anybody tried the above test version?

I tried the no$gba/no$psx test versions, but there's no crashing and task manager bugs in my Win10.

There's a stuttering audio bug in no$gba with NDS game.

Thanks for supporting CHD format!! It's working fine.

[Squaresoft74]

Anybody tried the above test version? I'd really like to get that problem sorted out!

Windows 10 22H2 x64:

Code: Select all

debug
tv
fonts
a
aa
b
bb
c
aspi
done

No crashing nor task manager bugs here.

[nocash]

All I get is

Code: Select all

debug
tv
fonts
b
bb

Thank you! That problem has been lurking around for several years, but now I know what hangs... it's this part:

Code: Select all

        MFG 'b'
 push offset patched_font_fname ;\remove font
 call RemoveFontResourceA       ;/
        MFG 'bb'
 push 0                         ; push 0                         ;
 push WM_FONTCHANGE             ; broadcast fontchange message
 push HWND_BROADCAST            ;
 call SendMessageA              ;/
        ;(hangs in above call)

That's coded exactly as recommended in the "Win32 Programmer's Reference", and I wouldn't have expected that the SendMessage call could hang... but actually it can happen, as described here: https://stackoverflow.com/questions/195 ... cast-hangs
Apparently you have another program that has locked up or refuses the handle it's message queue (you should theoretically see that in task manager, like tasks marked "not responding" or the like). And that's causing a ripple effect where the senders will also hang when sending broadcast messages to the hanging task.

I'll use SendNotifyMessage instead of SendMessage for broadcasts, that should work the same, but won't hang if any of the receivers fail to process the message (it might flood the message queue of the hanging task, but that's not my problem).

Bigger problem: The Win32 ref says that SendNotifyMessage isn't supported on win32s... so that function may kill support for windows 3.1 damnit : /
I haven't tested for a while, but the older no$xxx should work (or almost work) with win3.1 (when having the 32bit win32s upgrade installed). If neccessary, I could fallback to use SendMessage instead of SendNotifyMessage when detecting that old OS, but I don't currently have a PC set up for testing that stuff.

Windows 10 22H2 x64:

Code: Select all

debug
tv
fonts
a
aa
b
bb
c
aspi
done

No crashing nor task manager bugs here.

Good to know. Then it appears to be normally working, and only hangs if another task is hanging.

whenever I close NO$PSX, the program never closes properly. It closes the game window and disassembler, but the TTY output window hangs

The TTY window (and Help window and others) are normally automatically closed when reaching ExitProcess. Anyways, I've added code for closing them before ExitProcess yesterday (the main advantage is that it will now restore the keyboard focus to the correct window).

[Shadow]

Detecting the OS and applying the correct code to support it would be ideal, that way NO$PSX still works under Win16 systems. No point ditching Win16 support just because the exit code is broken on modern systems.

[nocash]

I am sure that win32s does at least require a 80386SX processor (hence the name: it's 32bit, and won't work on 16bit computers).
Btw. win32s was really rare ultra-odd exotic stuff, I doubt that more than 5-10 people (myself included) have ever used or supported it.
But yes, win32s support would be a neat nonsense feature, but detecting the OS without testing if that function (and other functions) are actually still working would be kinda pointless.

[Shadow]

By the way, version 2.2 is missing from here https://problemkaputt.de/psx.htm

[gwald]

I just tried 2.2 from the .de site, in winXP it crashes when launching via cmdline with a psx.exe as first param.
dragging and dropping seems to crash the same way.

[Shadow]

I just tried 2.2 from the .de site, in winXP it crashes when launching via cmdline with a psx.exe as first param.
dragging and dropping seems to crash the same way.

That's the same issue I'm having
I'll have to stick with V2.1 until NO$CASH can try it himself under Windows.

[Shadow]

Just an update regarding the broken volume levels. It seems I overlooked the volume slider ('Sound Volume' seen in my screenshot below) within the NO$PSX options. Sliding it back to full volume restored the issue. It operates independently from the Windows volume slider which is why I was so confused why I couldn't hear any audio output from NO$PSX anymore.

NO$PSX V2.2 however is still completely broken for me and fails to run any game (instantly crashes) which is why I've stuck with V2.1 for the time being.

[nocash]

This the wrong thread, for no$psx v2.1. I guess that's because the v2.1 thread is sticky and appears above v2.2.

I just tried 2.2 from the .de site, in winXP it crashes when launching via cmdline with a psx.exe as first param.
dragging and dropping seems to crash the same way.

Thanks! I'll fix that. No$psx v2.2 is allocating larger cue sheets, but the commandline loading did occur before doing that allocation.

Just an update regarding the broken volume levels. It seems I overlooked the volume slider... It operates independently from the Windows volume slider

No surprise then. Though I had thought that the newer windows versions would have that slider synced with one of the windows hardware mixer volume sliders.

[mkultimate]

They could add the FPS counter