I'm running Windows 10 32 bit on an HP elitedesk 800 g3 and was unable to boot to the nvme drive. I've got the bbs on the nvme drive, but the link on the sata drive (as all of the setups and batch files, etc. refer to c:\ele as the bbs directory and it would have taken an inordinate amount of effort (and even then I probably would have missed something) to change all of the references).
I'm running Windows 10 32 bit on an HP elitedesk 800 g3 and was unableto
boot to the nvme drive. I've got the bbs on the nvme drive, but thelink on
the sata drive (as all of the setups and batch files, etc. refer toc:\ele as
the bbs directory and it would have taken an inordinate amount of effort(and
even then I probably would have missed something) to change all of the
references).
I have no experience with Melee but something you have said is ringing a distant bell in my memory. I have had a few issues with programs not wanting to work with symlinked directories. Most programs don't care but some do, especially (but not always!) older ones. I am guessing it has something to do with how they interface with the operating system but, with those programs, you have to use the real physical path and not the symlinked ones in order for them to work.
It has been a while since I ran into that but that is my memory of things.
Sounds like your BBS is ok with that symlinking but, if possible, you may need to feed Melee the actual drive names and paths.
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 123 |
| Nodes: | 16 (1 / 15) |
| Uptime: | 10:25:58 |
| Calls: | 7,597 |
| Calls today: | 5 |
| Files: | 9,363 |
| D/L today: |
189 files (27,133K bytes) |
| Messages: | 390,136 |