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

Problems or feedback about the NO$PSX emulator by Martin Korth
User avatar
nocash
Verified
PSX Aficionado
PSX Aficionado
Posts: 422
Joined: Nov 12, 2012
Contact:

Post by nocash » December 8th, 2022, 3:57 am

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

User avatar
Shadow
Verified
Admin / PSXDEV
Admin / PSXDEV
Posts: 2635
Joined: Dec 31, 2012
PlayStation Model: H2000/5502
Discord: Shadow^PSXDEV

Post by Shadow » December 8th, 2022, 12:12 pm

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.
Development Console: SCPH-5502 with 8MB RAM, MM3 Modchip, PAL 60 Colour Modification (for NTSC), PSIO Switch Board, DB-9 breakout headers for both RGB and Serial output and an Xplorer with CAETLA 0.34.

PlayStation Development PC: Windows 98 SE, Pentium 3 at 400MHz, 128MB SDRAM, DTL-H2000, DTL-H2010, DTL-H201A, DTL-S2020 (with 4GB SCSI-2 HDD), 21" Sony G420, CD-R burner, 3.25" and 5.25" Floppy Diskette Drives, ZIP 100 Diskette Drive and an IBM Model M keyboard.

null
Active PSXDEV User
Active PSXDEV User
Posts: 60
Joined: Dec 18, 2021
PlayStation Model: SCPH-1002

Post by null » December 8th, 2022, 6:00 pm

nocash wrote: September 11th, 2022, 5:19 am 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.

User avatar
Squaresoft74
Verified
/// PSXDEV | ELITE ///
/// PSXDEV | ELITE ///
Posts: 300
Joined: Jan 07, 2016
PlayStation Model: SCPH-7502
Location: France
Contact:

Post by Squaresoft74 » December 9th, 2022, 6:42 am

nocash wrote: December 8th, 2022, 3:57 am 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.

User avatar
nocash
Verified
PSX Aficionado
PSX Aficionado
Posts: 422
Joined: Nov 12, 2012
Contact:

Post by nocash » December 9th, 2022, 8:04 am

Shadow wrote: December 8th, 2022, 12:12 pm 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.
Squaresoft74 wrote: December 9th, 2022, 6:42 am 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.
Shadow wrote: December 5th, 2022, 6:16 pmwhenever 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).

User avatar
Shadow
Verified
Admin / PSXDEV
Admin / PSXDEV
Posts: 2635
Joined: Dec 31, 2012
PlayStation Model: H2000/5502
Discord: Shadow^PSXDEV

Post by Shadow » December 9th, 2022, 12:38 pm

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.
Development Console: SCPH-5502 with 8MB RAM, MM3 Modchip, PAL 60 Colour Modification (for NTSC), PSIO Switch Board, DB-9 breakout headers for both RGB and Serial output and an Xplorer with CAETLA 0.34.

PlayStation Development PC: Windows 98 SE, Pentium 3 at 400MHz, 128MB SDRAM, DTL-H2000, DTL-H2010, DTL-H201A, DTL-S2020 (with 4GB SCSI-2 HDD), 21" Sony G420, CD-R burner, 3.25" and 5.25" Floppy Diskette Drives, ZIP 100 Diskette Drive and an IBM Model M keyboard.

User avatar
nocash
Verified
PSX Aficionado
PSX Aficionado
Posts: 422
Joined: Nov 12, 2012
Contact:

Post by nocash » December 9th, 2022, 1:30 pm

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.

User avatar
Shadow
Verified
Admin / PSXDEV
Admin / PSXDEV
Posts: 2635
Joined: Dec 31, 2012
PlayStation Model: H2000/5502
Discord: Shadow^PSXDEV

Post by Shadow » December 9th, 2022, 3:45 pm

By the way, version 2.2 is missing from here https://problemkaputt.de/psx.htm ;)
Development Console: SCPH-5502 with 8MB RAM, MM3 Modchip, PAL 60 Colour Modification (for NTSC), PSIO Switch Board, DB-9 breakout headers for both RGB and Serial output and an Xplorer with CAETLA 0.34.

PlayStation Development PC: Windows 98 SE, Pentium 3 at 400MHz, 128MB SDRAM, DTL-H2000, DTL-H2010, DTL-H201A, DTL-S2020 (with 4GB SCSI-2 HDD), 21" Sony G420, CD-R burner, 3.25" and 5.25" Floppy Diskette Drives, ZIP 100 Diskette Drive and an IBM Model M keyboard.

User avatar
gwald
Verified
1997 Yaroze Enthusiast
1997 Yaroze Enthusiast
Posts: 270
Joined: Sep 18, 2013
I am a: programmer/DBA
PlayStation Model: Net Yaroze
Location: Australia
Contact:

Post by gwald » December 28th, 2022, 11:20 pm

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.

User avatar
Shadow
Verified
Admin / PSXDEV
Admin / PSXDEV
Posts: 2635
Joined: Dec 31, 2012
PlayStation Model: H2000/5502
Discord: Shadow^PSXDEV

Post by Shadow » December 29th, 2022, 8:19 am

gwald wrote: December 28th, 2022, 11:20 pm 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.
Development Console: SCPH-5502 with 8MB RAM, MM3 Modchip, PAL 60 Colour Modification (for NTSC), PSIO Switch Board, DB-9 breakout headers for both RGB and Serial output and an Xplorer with CAETLA 0.34.

PlayStation Development PC: Windows 98 SE, Pentium 3 at 400MHz, 128MB SDRAM, DTL-H2000, DTL-H2010, DTL-H201A, DTL-S2020 (with 4GB SCSI-2 HDD), 21" Sony G420, CD-R burner, 3.25" and 5.25" Floppy Diskette Drives, ZIP 100 Diskette Drive and an IBM Model M keyboard.

User avatar
Shadow
Verified
Admin / PSXDEV
Admin / PSXDEV
Posts: 2635
Joined: Dec 31, 2012
PlayStation Model: H2000/5502
Discord: Shadow^PSXDEV

Post by Shadow » January 11th, 2023, 6:26 am

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.

Image
You do not have the required permissions to view the files attached to this post.
Development Console: SCPH-5502 with 8MB RAM, MM3 Modchip, PAL 60 Colour Modification (for NTSC), PSIO Switch Board, DB-9 breakout headers for both RGB and Serial output and an Xplorer with CAETLA 0.34.

PlayStation Development PC: Windows 98 SE, Pentium 3 at 400MHz, 128MB SDRAM, DTL-H2000, DTL-H2010, DTL-H201A, DTL-S2020 (with 4GB SCSI-2 HDD), 21" Sony G420, CD-R burner, 3.25" and 5.25" Floppy Diskette Drives, ZIP 100 Diskette Drive and an IBM Model M keyboard.

User avatar
nocash
Verified
PSX Aficionado
PSX Aficionado
Posts: 422
Joined: Nov 12, 2012
Contact:

Post by nocash » January 24th, 2023, 9:35 pm

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.
gwald wrote: December 28th, 2022, 11:20 pm 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.
Shadow wrote: January 11th, 2023, 6:26 am 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.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest