Any idea on why moving HIMEM in slot 0 doesn't work?

Pagina 2/3
1 | | 3

Van ducasp

Champion (350)

afbeelding van ducasp

25-06-2020, 21:39

zeilemaker54 wrote:

If you need to interact with other extensions which are using H.STKE as well, save the content of H.STKE somewhere, and install your own H.STKE handler. Your H.STKE handler should, after doing its own stuff, call the saved H.STKE.

Yeah, no problems doing hooks, use them a loot for the last 20 or so months Smile

Problem is that, ESE SCSI, at least the version that is used by BlueMSX, checks if H.STKE has anything other than C9, and if it is, it simply says not enough memory. I'll check if there is an update available for ESE SCSI bios that can be used with Blue MSX, that is my main test bed for this development. Tongue

Van ducasp

Champion (350)

afbeelding van ducasp

25-06-2020, 22:12

Just looked at the KERNEL that is loaded, and all three kernels I have from the disk I downloaded in MSX PRO have the same code, they load the contents of H_STKE in a, compare with C9, if it is not C9 they will halt. Do anyone know where to download / get the latest kernel available ?

Van Parn

Hero (603)

afbeelding van Parn

25-06-2020, 22:32

ducasp wrote:

I'll check if there is an update available for ESE SCSI bios that can be used with Blue MSX, that is my main test bed for this development. Tongue

Just out of curiosity, any specific reason not to use OpenMSX?

Van ducasp

Champion (350)

afbeelding van ducasp

25-06-2020, 23:05

Parn wrote:
ducasp wrote:

I'll check if there is an update available for ESE SCSI bios that can be used with Blue MSX, that is my main test bed for this development. Tongue

Just out of curiosity, any specific reason not to use OpenMSX?

I could quickly change BlueMSX source code to mimic the interface SM-X has between "MSX Slot" and ESP-01 (a module containing ESP8266 and flash memory and antenna) and redirect a serial port in my PC to it, so I just plug an ESP-01 with the firmware I've created on a serial USB adapter and can easily debug and code for it, that has increased the productivity of bug fixing and new feature creation tenfold, I've quickly tested several scenarios I could simulate on BlueMSX to fix a few UNAPI bugs, and now I'm almost finished with a rom version of the UNAPI driver, that might be the solid base of a really cheap MSX Accelerated Network Adapter. Wink

Van Grauw

Ascended (9271)

afbeelding van Grauw

26-06-2020, 01:44

ducasp wrote:

Just looked at the KERNEL that is loaded, and all three kernels I have from the disk I downloaded in MSX PRO have the same code, they load the contents of H_STKE in a, compare with C9, if it is not C9 they will halt. Do anyone know where to download / get the latest kernel available ?

So, if you plug in King’s Valley II with ESE SCSI present, it’ll also hang?

I can’t fathom why they would do that, intentionally halting on something that it should support.

Van ducasp

Champion (350)

afbeelding van ducasp

26-06-2020, 13:55

Grauw wrote:
ducasp wrote:

Just looked at the KERNEL that is loaded, and all three kernels I have from the disk I downloaded in MSX PRO have the same code, they load the contents of H_STKE in a, compare with C9, if it is not C9 they will halt. Do anyone know where to download / get the latest kernel available ?

So, if you plug in King’s Valley II with ESE SCSI present, it’ll also hang?

I can’t fathom why they would do that, intentionally halting on something that it should support.

Yes, it does, it calls DI and then HALT and in the screen you have the message "No enough memory"

More stupid yet, it seems even if you have ESE SCSI in SLOT 1 and Kings Valley 2 in SLOT 2 (ESE SCSI is loading first, so it gets H_STKE free) you still get an "No enough memory" Tongue

Van Manuel

Ascended (16846)

afbeelding van Manuel

27-06-2020, 00:03

Hey, that sounds familiar. I also see that often "No enough memory" and a halt. Not with ESE. But I can't remember what it was with....
Looking:
https://www.msx.org/forum/msx-talk/hardware/no-enough-memory...
https://www.msx.org/forum/msx-talk/hardware/ide-cf-card-error
Well, see https://www.google.com/search?q=site:msx.org+%22No+enough+me...

Ah yeah, I get it when running for example $ openmsx -machine Boosted_MSXturboR_with_IDE mg2.rom

So what is going on when you get this message?

Van ducasp

Champion (350)

afbeelding van ducasp

27-06-2020, 00:41

Manuel wrote:

Hey, that sounds familiar. I also see that often "No enough memory" and a halt. Not with ESE. But I can't remember what it was with....
Looking:
https://www.msx.org/forum/msx-talk/hardware/no-enough-memory...
https://www.msx.org/forum/msx-talk/hardware/ide-cf-card-error
Well, see https://www.google.com/search?q=site:msx.org+%22No+enough+me...

Ah yeah, I get it when running for example $ openmsx -machine Boosted_MSXturboR_with_IDE mg2.rom

So what is going on when you get this message?

I've checked and Metal Gear 2 doesn't seem to hook to H.STKE, so the problem is unrelated (even though yes, it seems that rom will cause a di halt on Open MSX if put in slot 2 using the boosted msx turbo r, but seems to work fine in slot 1).

Van KdL

Paragon (1324)

afbeelding van KdL

27-06-2020, 10:37

With 1chipMSX, Zemmix Neo and SM-X I always use the original cartridge of King's Valley II MSX2 with ESE-MEGASD kernel and it has never displayed the error "No enough memory".

Apart from that, I don't know if you've seen this example before: List A.1

Van ducasp

Champion (350)

afbeelding van ducasp

27-06-2020, 13:34

KdL wrote:

With 1chipMSX, Zemmix Neo and SM-X I always use the original cartridge of King's Valley II MSX2 with ESE-MEGASD kernel and it has never displayed the error "No enough memory".

Apart from that, I don't know if you've seen this example before: List A.1

Not specifically that link, but I've seen the code for h.stke, hclea and allocating memory before basic starts, nothing works WITH ESE SCSI, Hclea is never called if you boot DOS2 on it, h.stke is never called when ESE SCSI is running, it checks for it and freeze system if it doesn't have C9 (ret)

Not a big deal though, the way UNAPI works made a nice workaround possible, allocating memory on the first UNAPI call guarantees everything is done, basic, dos, etc And made it resilient to basic as well, can be used after returning to DOS.

As the idea is this to work on real cartridge as well as in SM-X, I don't want to alienate ESE SCSI users, UNAPI/Internet without mass storage is not really useful. :P

Pagina 2/3
1 | | 3