PS2 Open PS2 Loader will not use VMC files, please help.

[RFaction27]

Basically, Open PS2 Loader (I tried several builds, including one that until now has worked perfecly with VMC files) will not use VMC files. I tell it to use them in the OPL menu, but then it ignores them and just writes to the physical memory card 1.

I have been using FMCBoot, and Open PS2 Loader on my fat PS2 (model number SCPH-39003) for many years now, with an internal IDE hard drive, and it all worked great. All of my games worked fine from hard drive, and they all used the (brilliant) virtual memory card feature. I had two memory cards, both official Sony 8MB, and I was booting via FMCBoot v1.8 on the memory card in slot 2. For four years now, I have been using a 2018 build of Open PS2 Loader, as it did what I wanted of it, so I didn't bother to upgrade it, though from time to time I did try newer builds, but always kept the 2018 build on the memory card and as the one that I loaded from the FMCBoot ODSYS menu.

I was using a wired controller, but a few days back, I bought a wireless controller from Amazon. The wireless dongle goes into the first controller slot, of course, and when I did this, and booted the PS2, then the PS2 wouldn't recognize the controller, instead the LED in the dongle just kept on flashing, indicating that it hadn't synched/attatched to (or whatever the terminology is) the controller. But when I removed the second memory card (the one in slot 2, that boots via FMCB 1.8) so that my PS2 was now not soft-modded, then when I booted up the PS2, then the dongle stopped flashing immediately, and the wireless controller worked perfectly.

So I assumed it was a problem with FMCB, and, hoping that a later version of FMCB would fix it, I download the latest version of FMCB that I could find, from:

https://sites.google.com/view/ysai187/home/projects/fmcbfhdb

which is listed as version v1.966, though on the booted up ODSSYS menu it says version 1.987.
I then backed up my second memory card, the one that I was booting from with FMCB 1.8, using two methods. I used Memory Card Annihilator v2.0 to create a disc image of the physical memory card, and I also manually copied all of the files from the physical memory card to a USB stick, thereby giving me (I assumed) two ways to return the memory card to it's working, booting from FMCB 1.8 state if anything went wrong.

I then installed Free McBoot 1.966 (or 1.987?) on that memory card, rebooted the PS2, and success! The PS2 booted up, and now I could use the wireless controller. And the games loaded correctly from the hard drive (using the 2018 version of Open PS2 Loader, since I'd not altered anything on the card aside from installing FMCB v.1966 over the v1.8 version, and editing the FMCB menu to include things like the homebrew game Geotron v0.5) and everything seemed fine. But then I noticed that the games were no longer saving to the virtual memory cards, but to the physical memory card in slot 1 (not the FMCB booting memory card, of course, that is still in the second controller slot).

All of the VMC files still seem to be on the hard disc (they are all still listed as being there, and being the correct 8MB in size each), which I checked with uLaunch. And even if they had been deleted (I did NOTHING at all to the hard drive, or to delete the files) then when I deleted the VMC in Deus Ex, and created a new one, then the VMC feature should have worked then, but again, the game just wrote to the physical memory card.
I removed the wireless dongle, and plugged in my wired PS2, in case that was somehow causing Open PS2 Loader to not use VMC files, but it didn't fix the problem. From then on, I've not used the wireless controller, everything following this is with the wired controller, though I doubt that would make a difference.

I tried two new versions of Open PS2 Loader, with the same results; everything is fine except that the VMC function now no longer works. Searching the forums, I found that someone had posted the following solution when having the same problem:

https://www.ps2-home.com/forum/viewtopic.php?f=32&t=2906

That worked for them because their problem was caused by their +OPL partition being full. But when I checked, my +OPL was (I think) 2GB in size, and only about two thirds full. Still, I enlarged it anyway, but I still can't get the VMCs to be used by Open PS2 Loader.

Once again, I stress that I was using the four year old version of Open PS2 Loader with v1,8 of FMCB (which booted from the memory card in slot 2 of my fat PS2), and the VMC function was working properly (and I used it for every game). Then when I upgraded FMCB to v1.966 (which fixed the wired controller not working problem) that was the only change I made, other than adding a few links to the FMCB OSDSYS menu. I didn't alter the Open PS2 Loader version, or alter the hard drive contents in any way. I didn't alter the physical, booting memory card in any way except for the FMCB update. The four year old Open PS2 Loader files are on that memory card, and I did not alter them, but now that version of Open PS2 Loader will not use VMC Files. I've also tried two recent builds of Open PS2 Loader, and they perform the same as the four year old version, in that they load all the games OK, but always access the first physical memory card even though in their options screen they show that a VMC file is being used.

So I though I would revert my second memory card (the one I boot with, in the second controller slot) back to how it was pre-installation of FMCB 1.966, so that hopefully I could use VMC files again, albeit without the wireless joypad, so I restored my backup image of the second memory card (which I had made using Memory Card Annihilator v2.0, just before I installed FMCB v1.966) onto my FIRST memory card.

I wanted to keep the second memory card, which is the one now booting with FMCB v1.966, as it is working find aside from the VMC problem, so I thought I would leave it in case I found a cure, and so I used first memory card, to effectively turn it into a copy of the second memory card as the second memory card had been when I made the disc image from it.

So then I removed the second memory card from the PS2, and tried to boot from the first memory card. But for some reason the first memory card wouldn't boot. It just keeps the PS2 on a black screen, until I remove the memory card, and then the PS2 boots up in a non-soft modded state, due of course to no memory card being present. Yet the first memory card should be a copy of the second memory card back when it (the second card) booted up in FMCB 1.8 then ran Open PS2 Loader from four years back and worked properly with VMC files.

So, using Memory Card Annihilator v2.0, I formatted the first memory card, then copied the files from the file by file backup that I had made onto my USB memory stick, back onto memory card 1. But it still won't boot, and has the same symptoms; It just keeps the PS2 on a black screen, until I remove the memory card, and then the PS2 boots up in a non-soft modded state.

I thought maybe memory card 1 was faulty, so I bought another one (again, an official 8MB Sony card), let's call it memory card 3, and after restoring either the memory card 2 image, or file by file copying, then memory card 3 behaves exactly the same as memory card 1, a black screen and the PS2 not booting until I remove the card). Why would both types of backup, the disc imaging, and the file by file copying, fail? I haven't tried either of these methods on memory card 2 as I'd like to keep it as it is in case I find a cure for the VMC problem, as I have configured it to load so many menu items.

Can anyone advise me on what might be causing the VMC problem, please? The virtual memory card function is so convenient and useful that I use it for every game, and I'd hate to not be able to use it.

Thanks for reading this, and for any help or advice.

 

[Berion]

I tell it to use them in the OPL menu, but then it ignores them and just writes to the physical memory card 1.

You must turn on VMC in options, setting per game. Filename must match to GameID, or use generic, or edit game cfg by hand to match vmc filename.

Here are official builds of OPL:
https://github.com/ps2homebrew/Open-PS2-Loader/releases

So I assumed it was a problem with FMCB, and, hoping that a later version of FMCB would fix it, I download the latest version of FMCB that I could find, from:

FMCB/FHDB is currently dead, so no new versions in the future.

In near (?) future, You will get alternative called XEB+.

which is listed as version v1.966, though on the booted up ODSSYS menu it says version 1.987.

Version string is written in FMCB config file. During installation, config is adopted, not replacing.
"OSDSYS" (On Screen Display System?), not "ODSSYS". ;]

I used Memory Card Annihilator v2.0 to create a disc image of the physical memory card, and I also manually copied all of the files from the physical memory card to a USB stick, thereby giving me (I assumed) two ways to return the memory card to it's working, booting from FMCB 1.8 state if anything went wrong.

MCA do not creating disc images, especially from Memory Cards. It creates Memory Card images from Memory Cards. And this is the proper way of having backup of Your whole setup.

Copying files from filesystem via file manager (i.e by wLE/uLE) is still ok and can be used but symlinks from MCFS cannot be recreated that way.

using the 2018 version of Open PS2 Loader

There is no such thing like "2018 version". Each build have it's number like i.e latest 1828 and stable versions releasing from time to time getting versioning like i.e version "0.9.3" or "1.1.0". Should be displayed in About in OPL.

Still, I enlarged it anyway

And probably break it in the process.
https://www.psx-place.com/threads/wlaunchelf-release-thread.13727/page-12#post-314650
https://www.psx-place.com/threads/wlaunchelf-hddmanager-partition-expanding-test.35704/

I wanted to keep the second memory card, which is the one now booting with FMCB v1.966

Executables for OSD Update feature (which FMCB exploiting) are signed. And signing is per physical device due how Magic Gate works here, it will not boot from another device. So if You made image with one MC and restore it on another MC, this second one will not boot to FMCB because firmware PS2 will reject it as improperly signed.

You can "fix it" by replacing kbit and kc section in all *.elf files inside "mc?:/BxDATA-SYSTEM/" and "mc?:/BxDATA-DVDPLAYER/" to match target Memory Card. Yet easiest/quickest way is just to reinstall FMCB.



PS: You should earn gold medal of problem description.

 

[RFaction27]

Hiya mate, thanks for answering.

You must turn on VMC in options, setting per game. Filename must match to GameID, or use generic, or edit game cfg by hand to match vmc filename.

Yes. I've been using OPL with VMC memory cards for a few years now, with no problems. I've always created the VMC file for a given game via the individual game settings (press TRIANGLE when the game is highlighted in the game menu), and then the game just uses the VMC file automatically, with no further prompting from me.

It's only since I updated FMCB and tried a modern version of OPL that OPL (old and modern) are not using the VMC files, and instead are using the physical memory card slot 1 instead, although the VMC file is set in the game's individual game setting menu in OPL.

There isn't a universal "Use VMC files" option somewhere in OPL is there? I can't find one, or remember using one when I first set up my PS2 and FMCB/OPL all those years ago. Does OPL not produce a log file, that might point out the problem to us?

The automatically generated filename for the VMC file is the game's ID but with a '_0' suffix. I.e., for Deus Ex: The Conspiracy, the game ID is 'SLUS_201.11', and the VMC is named 'SLUS_201.11_0'. I deleted this file (via the OPL game setting menu), and recreated it, but it still didn't work.

Using ulaunch, I looked at:

hdd0:/ +OPL / VMC

and the VMC file is there, as it should be. So I don't think it's a problem with the VMC files not being created, or the path OPL uses to access those files.

Here are official builds of OPL:
https://github.com/ps2homebrew/Open-PS2-Loader/releases

Thanks. I've just downloaded and tried v1.1.0 from there, but it's showing the identical problem to the other versions I've tried; it's not using the VMC files, instead it just tries to use the first physical memory card slot.

FMCB/FHDB is currently dead, so no new versions in the future.

In near (?) future, You will get alternative called XEB+.

Interesting. I will keep an eye on that.

Version string is written in FMCB config file. During installation, config is adopted, not replacing.
"OSDSYS" (On Screen Display System?), not "ODSSYS". ;]

I see, thanks.

MCA do not creating disc images, especially from Memory Cards. It creates Memory Card images from Memory Cards. And this is the proper way of having backup of Your whole setup.

Sorry, I was just being careless, and typing 'disc image' from force of habit.

Executables for OSD Update feature (which FMCB exploiting) are signed. And signing is per physical device due how Magic Gate works here, it will not boot from another device. So if You made image with one MC and restore it on another MC, this second one will not boot to FMCB because firmware PS2 will reject it as improperly signed.

That makes sense. I've just reverted memory card 2 to the image I made of it before I updated FMCB, and it's now just as it was when I made the memory card image, thanks for letting me know that each memory card had a unique id or something (I don't know the details of Magic Gate), I just assumed (stupid me!) that one 8MB official card seemed exactly the same as another to the PS2.

Unfortunately, even though I can now load the same FMCB/OPL setup from memory card 2,and so should be able to use VMC files, the VMC files are not working. Even though memory card 2 is identical to what it was when it was working with VMC files.

And probably break it in the process.
https://www.psx-place.com/threads/wlaunchelf-release-thread.13727/page-12#post-314650
https://www.psx-place.com/threads/wlaunchelf-hddmanager-partition-expanding-test.35704/

Damn. I hope there hasn't been any corruption, but I won't know until I get the VMC feature working.

PS: You should earn gold medal of problem description.

Yes, sorry my post was so long, but I wanted to include everything that I thought might be relevant.

 

[Berion]

Yours problem for sure is related to OPL configuration (I doubt) or HDD. Best test IMO for this will be:

1. rename "+OPL" partition to something else i.e "OPL_old" (in uLE, go to HDD Manager and from there You can i.e rename any partition)
   
2. be sure that You have at least 128MiB of free space because OPL will create +OPL in that size by default if not found +OPL (and we don't want him to find for test purposes)
   
3. copy config files and one test VMC in proper places to this new created partition
4. run OPL (version doesn't matter as long as it is official OPL and support VMC)

If this will fix the problem, it means that "OPL_old" is corrupted. Remove it then, perform a scan by HDDChecker and have finger crossed it will not make further damages in partitions chain (if You have some games installed only on HDD, just in case try to copy them back to PC).

If it will not fix, then delete all config files and try again set the VMC and run the game. This prove that problem lies in configuration (maybe some bug from old parram or their combination?).

There isn't a universal "Use VMC files" option somewhere in OPL is there?

I don't remember TBH. I barely using OPL and VMC.

Does OPL not produce a log file, that might point out the problem to us?

No. Only debug colours but this is related only to game booting process.

Sorry, I was just being careless, and typing 'disc image' from force of habit.

I'm just man of details. ;p

I just assumed (stupid me!) that one 8MB official card seemed exactly the same as another to the PS2.

Memory where data is stored is exactly the same. Only security is different. So You can use such backup and card after such restoration and this will be exactly the same stuff as on backup card, but booting will not work until booting elfs will be signed for new device.

They designed Magic Gate to earn extra money on it. Otherwise they would just allow user to use formatted USB devices with MCFS as standard MCs but then, no one would buying them (and MCFS is slower the larger card is; some people says also that few games have problems with larger VMC/cards). And the same with PSP. Instead of use cheap microSD, they goes with ugly MSPD. Anad again they did the same shit with PSV/PSTV but this time, this ship has sunk.

There is no really any technical reason why Magic Gate is needed, so it is not stupid, it is logical. MG is piece of shit which kept unlicensed producers away for a long enough to scam us the players.

Yes, sorry my post was so long, but I wanted to include everything that I thought might be relevant.

It's not an accusation. This how people should describing problems instead:

yo hi doesnt work
help!!!1111!!!!!1

 

[RFaction27]

Yours problem for sure is related to OPL configuration (I doubt) or HDD. Best test IMO for this will be:

1. rename "+OPL" partition to something else i.e "OPL_old" (in uLE, go to HDD Manager and from there You can i.e rename any partition)
   
2. be sure that You have at least 128MiB of free space because OPL will create +OPL in that size by default if not found +OPL (and we don't want him to find for test purposes)
   
3. copy config files and one test VMC in proper places to this new created partition
4. run OPL (version doesn't matter as long as it is official OPL and support VMC)

If this will fix the problem, it means that "OPL_old" is corrupted. Remove it then, perform a scan by HDDChecker and have finger crossed it will not make further damages in partitions chain (if You have some games installed only on HDD, just in case try to copy them back to PC).

You've found the problem! I did as you said, and Open PS2 used the virtual memory card as it should do. I ran HDDChecker (thanks for letting me know about this, I didn't know there was a workable disc checking program on the PS2), and it found and fixed problems.So I tried to copy the ART, CFG, VMC etc folders from the hard drive to the USB memory stick so I had a back up of them, but the copy failed and unLaunch couldn't see the ART folder (the hard drive's folder tree just stopped showing up in uLanuch). So I reset the PS2, then uLaunch saw the hard drive again, so I ran HDDChecker, it found and fixed the errors, and then uLaunch saw the hard drive no problem, but when I then tried to copy the ART folder then uLaunch again reported a copy failure, and couldn't see the hard drive.

So it looks like the hard drive is on the way out. And finding a replacement isn't going to be easy, since IDE drives have long been out of production. I know that PS2s can use SATA drives, using a converter, but I don't know anything about this. Would you know anything about this? Does it require anything special about the SATA hard drive? A special IDE to SATA converter, or will they all work? Does the converter itself need a power supply, and do the SATA hard drive and the converter both fit inside the PS2, do you know? Is there a good guide on what to purchase and how to set it up for the PS2 and Open PS2 Loder? Any advice would be gratefully received.

I don't remember TBH. I barely using OPL and VMC.

Do you not use a PS2 anymore? Or do you use one with network game loading?

No. Only debug colours but this is related only to game booting process.

I find that a little surprising. I would have thought that a log file would help in such a big project (all of the PS2 games (including variants) multiplied by the number of potential hard drives multiplied by whatever other variables there are), to narrow down the causes of a particular problem or glitch.

Memory where data is stored is exactly the same. Only security is different. So You can use such backup and card after such restoration and this will be exactly the same stuff as on backup card, but booting will not work until booting elfs will be signed for new device.

I see, thanks.

They designed Magic Gate to earn extra money on it. Otherwise they would just allow user to use formatted USB devices with MCFS as standard MCs but then, no one would buying them (and MCFS is slower the larger card is; some people says also that few games have problems with larger VMC/cards). And the same with PSP. Instead of use cheap microSD, they goes with ugly MSPD. Anad again they did the same shit with PSV/PSTV but this time, this ship has sunk.

There is no really any technical reason why Magic Gate is needed, so it is not stupid, it is logical. MG is piece of shit which kept unlicensed producers away for a long enough to scam us the players.[/QUOTE]

Well, Sony really needed the extra money [/sarcasm]. Not that Nintendo or Microsoft are much different, of course.

It's not an accusation. This how people should describing problems instead:

Thanks!

 

[Berion]

So it looks like the hard drive is on the way out.

It looks like broken filesystem on that partition. Try copy it via PFS Shell or PFS Fuse on PC if those data are important to You.

To determine HDD condition, check his S.M.A.R.T. on PC.

I know that PS2s can use SATA drives, using a converter, but I don't know anything about this. Would you know anything about this?

There is better solution than You thinking. Using Network Adaptor board replacement. I.e Bitfunx 2.0 (avoid GameStar).

and how to set it up for the PS2 and Open PS2 Loder? Any advice would be gratefully received.

I don't understand question. You need format drive to APA and install games which You have etc. etc.

https://www.psx-place.com/threads/a...thing-you-should-know-about-hdd-in-ps2.30912/

Do you not use a PS2 anymore? Or do you use one with network game loading?

I'm using, but rather not for playing games. I finished all which are interesting to me ~18 years ago.
Sometimes when I discovered some new title with potential, I just prefer real MC as I have it always connected anyway (FMCB boots faster than FHDB).

Not that Nintendo or Microsoft are much different, of course.

Yes, they all are MFs now.

 

[RFaction27]

Thanks for the answers, mate.

It looks like broken filesystem on that partition. Try copy it via PFS Shell or PFS Fuse on PC if those data are important to You.

To determine HDD condition, check his S.M.A.R.T. on PC.

I will look into PFS Shell and PFS Fuse, thanks. I'm *think* the hard drive passed the SMART test on the PC, but I might check to make sure.

BTW, I take it that modern versions of Open PS2 Loader use a 'CFG' folder, and not a 'CFG-DEV' folder, as OPL seemed to use for a while.

There is better solution than You thinking. Using Network Adaptor board replacement. I.e Bitfunx 2.0 (avoid GameStar).

I hadn't heard of the Bitfunx, but it looks good. I will read up on it (and avoid the GameStar type, thanks).

I don't understand question. You need format drive to APA and install games which You have etc. etc.

https://www.psx-place.com/threads/a...thing-you-should-know-about-hdd-in-ps2.30912/

I just thought that if I used an SSD drive instead of a SATA, then maybe some PS2 software that worked with IDE wouldn't work with SSD, so I'd need different software, sorry.

So far, I've always used WinHIIP; I connect the PS2's IDE hard drive to my PC, then use WinHiip to transfer the PS2 games to the hard drive. But I've been looking on the forums, and HDL Batch Installer seems (to me) to be the best modern solution, would you agree?

I'm using, but rather not for playing games. I finished all which are interesting to me ~18 years ago.
Sometimes when I discovered some new title with potential, I just prefer real MC as I have it always connected anyway (FMCB boots faster than FHDB).

I see. I'm just a gamer, PS2-wise. But I do love the homebrew scene, it's brilliant how people manage to add to the functionality of old machines, and also get other games and emulators to run on them.

 

[Berion]

You can use IDE or SATA HDD/SHDD/SSD but there is a catch related to SATA speed and the adaptor replacement itself (as I mentioned in the tutorial). If drive making issues with OPL, try use MDMA read mode (or slowing down hard drive by jumper if You have such possibility), but this depend of adaptor somehow. Some people reports it helps, some saying it works without any above voodoo.

WinHIIP cannot be used if HDD is 1TiB or larger because it breaking APA chain after exceeding this barrier. So use instead HDL Batch Installer.

The main reason I no longer playing games (like i.e hacks/translations) is that I cannot stand blurry image. I don't have CRT and I don't want it. GSM+Component cable doesn't solve it, so I would need external (OSCC etc.) or internal (PS2Digital) hardware upscaller which they cost small fortune.

 

[RFaction27]

Hiya!

You can use IDE or SATA HDD/SHDD/SSD but there is a catch related to SATA speed and the adaptor replacement itself (as I mentioned in the tutorial). If drive making issues with OPL, try use MDMA read mode (or slowing down hard drive by jumper if You have such possibility), but this depend of adaptor somehow. Some people reports it helps, some saying it works without any above voodoo.

OK. I'll let you know if I have any problems.

WinHIIP cannot be used if HDD is 1TiB or larger because it breaking APA chain after exceeding this barrier. So use instead HDL Batch Installer.

Will do, thanks.

The main reason I no longer playing games (like i.e hacks/translations) is that I cannot stand blurry image. I don't have CRT and I don't want it. GSM+Component cable doesn't solve it, so I would need external (OSCC etc.) or internal (PS2Digital) hardware upscaller which they cost small fortune.

Tell me about it. No TV manufacturer seems to care about retrogaming, let alone actually bother to say whether or not their shiny new TVs will display older resolutions and standards. My oldest console is my N64, and it's output on my current TV (a three year old LCD) is all but unusable. I bought a RetroTink for it, and now it's OK. Not great, but that's because a PAL N64 outputs a nerfed picture anyway, at least by the time the signal leaves the video out port. I wanted to get an UltraHDMI mod for the N64, which gives amazing results since it gets the signal directly from the N64's video hardware, but with the cost of the mod, plus the cost of it's installation into my N64, plus the cost of sending my N64 there and back, it would have cost well over twice the price of the RetroTink. But the N64 is my favourite console, so I had to get it working on my TV.

BTW, being a PAL gamer was always a curse. The games usually came out later than their NTSC equivalents, and sometimes they were bad NTSC to PAL ocnversions (Super Mario 64, and Mario Kart 64 were two every early N64 examples, the PAL version of SM64 is slower and has black borders instead of being full screen, and MK 64 was around 17.5% slower than the NTSC version, meaning that PAL gamers couldn't compete against NTSC gamers when comparing their best lap times). And there were always good games that didn't appear in PAL at all.

 

[Berion]

All TV can display consoles output, but the problem is, those low resolutions must be upscaled to native resolution of TV matrix. When it is done by Nearest Neighbour algo with correct Aspect Ratio, then image is near to perfectly crisp, even better than in old times because of no scanlines. But... none of those TV doing that, they just stretching image using algorithms which don't look good with games, especially with pixelart. So instead crisp image, we getting blurry shit. And here is why such external upscallers was designed for (they eating console's native resolutions, upscalling it by the settings chosen by user and output target resolution for TV which he just displaying it).

Yeah, RetroThink is one of the best choice on the market now (based on YT reviews).

Internal upscallers are the best in theory but imagine that You install such to N64 and he output great image in 1080p. But many many years later You have bought TV with 8K. So TV will scale it 4 times and loose much of quality. The same with external upscallers (if their hardware is to weak to handle such image processing and/or authors will not release his fw update) but You can still sell it without any soldering etc.

 

[RFaction27]

You can use IDE or SATA HDD/SHDD/SSD but there is a catch related to SATA speed and the adaptor replacement itself (as I mentioned in the tutorial). If drive making issues with OPL, try use MDMA read mode (or slowing down hard drive by jumper if You have such possibility), but this depend of adaptor somehow. Some people reports it helps, some saying it works without any above voodoo.

I thought I'd play it safe, and buy an IDE drive. More expensive for less storage capacity, admittedly, but I've always been unlucky, so I thought I'd stick with what had worked for me. The largest I could find was a 320 GB, for £48, so I bought it. And it won't fit onto my PS2 network card.... It turns out that Western Digital hard drives (some, at least) have a wider space between the power and data slots than other hard drives, so the network adapter's spacing isn't flexible. See what I mean about my (lack of) luck?

I've found a couple of guides showing how to strip down the network adapter, separate the power and data slots sufficiently, and slightly modify the metal face plate:

https://ps2drives.x-pec.com/?p=guide_westerndigital

but I'll leave it to tomorrow. Why does life continually throw us a series of petty problems? Presumably to take out minds off the series of huge problems that life also throws at us?

 

[Berion]

Oh yeah, that's an issue. Sometimes, IDE and Molex ports are not extremely spaced from each other and using force can fit but... That's unnecessary risk and anyway, it will kill the soldering sooner or later. The is no good solution here. It's hard to assembly such contraption as on YT film, especially that NA port must perfectly put into PS2 or else she will not detect it. Good luck! ^^