512k, last line. And "Base RAM" is included (second line) into these 512k, located in the same subslot.
There may be other RAMs in your machine, but TestRAM does not show it. It shows the RAM configured as primary.
Another conundrum when using ericb59's ROM base script as shown here.
I tried to update by pressing F1 and it spits out this error message: Line buffer overflow
I ignored the update procedure for now and selected a random ROM file (say, Nemesis Gradius 2 JP). The system then spits out another error message: Device I/O error in 3000
I guess line buffer overflow error must also come with line number. This error is not (at least directly) related to gr8net but rather saying that string is too long. Would be good to know the line it occurs in and perform output of the variables at the time of error.
The cause of Line buffer overflow error when program is being loaded is the trailing EOF character in the text file (that's why there's no line number in error - because it happens at the direct statement). I downgraded to version 0.8 to see if there's something wrong in newer versions, and got the same result. If I remove this character the program loads without problem.
Thus this was always in there, no one just caught it (probably no one was running this BASIC program for a while). I always use browser to load BASIC programs (faster). According to HTTP headers the last modification to the program was at "Sat, 02 Jul 2016 14:49:18 GMT", 5 years ago! I think a long time ago I changed the behavior to handle binary transfers, and EOF character is now being treated as just binary char, and not as EOF.
I am actually more concerned about Direct statement in file error I sometimes get when program is being loaded using LOAD. Does it happen to you too?
New update.bin image is on the website, please update, and try running Eric's program again. It runs for me now (however hangs when I select Metal Gear 2, but it is next problem).
In line 3000 program assumes that adapter active is #0. If not, it throws Bad file name. The fix is to remove zero in the device name to use default adapter.
Regarding Device I/O error in line 3000 more information is needed. Please contact me through email or facebook.
I will update manual on using BASIC access (LOAD/OPEN etc) for text and binary access.
I am actually more concerned about Direct statement in file error I sometimes get when program is being loaded using LOAD. Does it happen to you too?
It appeared to be related to the problem with my machine. I disassembled it, tested all caps in power supply, cleaned slot and power connectors with spirit... did not help much. Seems the connector wears out as I inserted the boards a lot of times, maybe several thousands times...
I also updated Eric's program with the selection of adapter is several are in the system, removed the explicit pointing to adapter 0, and sent the program back to Eric.
MG2 does not start without reset (with CAPS key off) seems to be normal because tool tries to start the ROM without reboot, and ROM does not like it.
I also made required modifications to the network file input routine, now if file is OPEN""AS# then the access is binary, but if OPEN""FORINPUTAS# then access is in text mode and EOF char is treated as end of the stream.
