nfg.forums

We may have ruined things for everyone.

Gimons:
今回PhantomXを購入していただいた中で海外の方の比率が最も高かった気がします。このような状況を鑑みると必要な方にはほぼ行きわたったと思います。今回がまとまった頒布としては最後でしょう。

(This time, I feel like the proportion of overseas buyers among those who purchased PhantomX was the highest. Considering this situation, I think it's probably reached almost everyone who needs it. This will likely be the last major distribution.)

This is a drop-in replacement for the existing PCB in a Hori Fighting Stick V3 (Not the RAP V3-SA).  You should be able to just unplug the existing cables in the stick and plug them into this board and get playing. 


There are two caveats:

• It does not support the auto-fire sliders at all.
• There are two revisions of the FS V3 stick

If your stick has four connectors on the PCB, this will work.  If your stick has two connectors on the button board, one running to the main PCB and one running to the top AUX panel) it will not work.

This board is untested but I've checked everything about 400x and I'm pretty confident it'll work fine. 

The connectors used in this stick are clones of the JST PH-series connectors, made by LHE.  The GP2040 board used is a Waveshare RP2040 Zero.

This is my first PCB design, if you can see any errors or ways to improve it, please let me know.  The attached zip file includes the gerbers, enough that JLCPCB has no trouble generating a board from it. 

There are no restrictions on the use of this design, do as you like with it.

its a shame the icons get lost

Quote from: leonk on January 24, 2026, 07:05:06 PM... and it's sold out. I believe the extended memory is used by much more modern OS's (eg BSD/Linux running on the X68000) Stuff from back in the day won't use it because that memory range never existed before.

The x68030/060 FMV games all use that extended memory, and do so under Human68k

I have a lir2032 as battery, and a good SRAM, and also rom with ipl1.6 that automatically detect the ram onboard and adjust the system 😁

P.s.: my above tests with bluescsiv2 and sasi images were based on my ace hd, planned testing on c600z for next days

edited: @kamiboy ,  if you want to configure ram without changing the rom, you could simpli add to autoexec.bat a line like:
switch memory=10240

Can confirm that the power switch on my ACE functions perfectly fine without a battery.

I don't suppose there is a way to set the memory size switch on boot every time. Should be possible to dump the SRAM once after setting the memory switch to the correct amount then write back to the correct memory space every time on boot, that should take care of that.

Quote from: kamiboy on January 26, 2026, 05:52:46 PMThis way I will forego the SRAM trick entirely and have an image set that boots and works out of the box on any of my SASI X68000 machines. I won't bother re-fitting them with SRAM batteries at all. The only disadvantage would be that the dates won't be right, but who cares.

Isn't the battery still needed for RTC to work which in turn is needed for properly functioning power switch? Lack of battery will also mean you'll need to setup memory sizes on every boot.

Did a quick test just changing id:0 to id:1 in @incrediblehark sasi boot drive's config.sys, and had both sasi and scsi mapped at boot, and launched sxwindow from image 3.02!
So, it's just a matter of mapping drive and rearrange boot sys & bat files

Excellent. I will test as soon I am home from work. For my part I think I want to make a 40mb SASI image that contains all Human68K system files, tools as well as autoexec and config.sys, so it will be the dedicated OS drive, which boots, loads SASI drivers, etc. Then SCSI drives 1-X will just contain games and other data.

This way I will forego the SRAM trick entirely and have an image set that boots and works out of the box on any of my SASI X68000 machines. I won't bother re-fitting them with SRAM batteries at all. The only disadvantage would be that the dates won't be right, but who cares.

Eric wrote me that he'll open a new issue and he'll include the fix in next releases.
I'm not a x68000 programmer, but it could be a first step for loading in ram instead of in sram the scsi driver?
With scsi driver loaded, i found the sasi drive mapped at i:.
Edited:
I mean.. what about a masterdisk v4 with scsi driver loaded and mapped for all scsi drives, and a remapped Image v.3.02?