JST Kickstart 1.3

[dr.zeissler]

I'll do some tests with preinstalled WHD-Slaves for OCS/ECS Demos.

[dr.zeissler]

Just tested ARTE demo and it works! that's great!

[jotd]

6MB RAM you could softkick for whdload, well, barely, if the game is really big.

[jotd]

I just tested Wiz'N'Liz on JST 6.1 and winuae and it works. Where does it crash?

BTW fixed 2 serious bugs, now Slamtilt & Bloodwych run. I made myself a "slave wrapper" to record in/out values of JST/WHDLoad calls & compare. that'll help!

[dr.zeissler]

Odysee-Demo is to big to load with JST, can I do something?

[jotd]

Yes, you could use HDLOAD tooltype. If the demo is made of diskfiles, that could work.

[turrican3]

Originally Posted by jotd

mmu=laxist: jst. whdload:mmu=none

@dr.zeissler: you should use whdload slaves. They are updated for controls, fixes, features... JST slaves aren't updated anymore (I don't even have the means to build them anymore personally)

Hi jotd,
i remembered to have a big boost with mmu=laxist but not with mmu=none (whdload) ??? A reason ?? Or is it my bad memory ???

[jotd]

I'm really not sure about this MMU crap. MMU is still a mystery (to me, because I never really got into it).

[matburton]

Sorry for the slow reply life got in the way

I just tested Wiz'N'Liz on JST 6.1 and winuae and it works. Where does it crash?

Hmmm... odd. I'll retest it tonight. It was crashing pretty much immediately.

Was that with Kickstart 1.3?
Was that with the OCS chipset? (but with 1MB chip ram)

[jotd]

if the games use to run with OCS+1MB chipmem, they'll run with JST. Kickstart 1.3 is supported by JST for users who cannot/don't want to softkick on their old A2000 or A500 HD

[matburton]

Wiz 'n' Liz only required 0.5MB chip and 0.5MB fast.

I assumed that to be safe JST would need 1MB of chip for most games given that Workbench is still in memory in the background?

Sorry I meant to re-test last night but dozed off will re-test tonight!

[matburton]

So here's a capture of Wiz 'n' Liz with 6.0 compared to 6.1



6.0 plays the game fine, 6.1 crashes in odd ways before even the logo is shown

Anything more useful I can provide? Save states, disk dumps etc?

[jotd]

JST is able to perform a "no return" if there isn't enough mem available. Or did I remove the "feature" ? I dunno.

Wiz'n'Liz works for me on 6.1... and JST isn't good at catching exceptions (lots of features have been broken / removed through the years, so I don't know)

[Kickstar]

Hello great project.
Give it a Launcher like Igame or tiny launcher for Workbench 1.3 to start the JST games?

[jotd]

I'm not going to write a 1.3-compliant launcher, that's for sure. If you have room for the launcher, maybe you have room for softkicking?

[matburton]

Hey Kickstar,

Although I think jotd has mentioned that launching JST from workbench rather than the CLI is somewhat unrelaible at the moment I've found it to work the same as the CLI in all cases I've tried.

Hence if you just want some icons to avoid using the CLI then you could create some Project .info files, with your choice of icon(s), and assign JST as the default tool. The options that JST supports work in the same way as WHDLoad, using the tool types in the .info file.

It's certainly the way I've been launch my games and demos using JST

Shout if you want any further help.

If you do have any problems launching JST from workbench then IconJ or CLICon are both viable work-arounds and work under 1.3

[jotd]

... and the CLI launch doesn't seem too great either. But I was unable to reproduce the slave filename truncation issue, or I'm unable to figure out why it would happen in the code.

[matburton]

... and the CLI launch doesn't seem too great either. But I was unable to reproduce the slave filename truncation issue

In fairness I found it very tricky to reproduce after I first encountered it so it's still pretty darn great

Is there any way I can zip-up and send you a complete WinUAE save state in a reproduction state later this week jotd?
Or is that realistically not going to help find the root cause of this particular problem?

[jotd]

savestate will do: I can use memory watches to find which part is clobbering the file name. You can zone it.

[matburton]

Hey jotd,

I've uploaded a file called

jst-6.1-file-name-truncation.zip

to The Zone!

You'll need to do the following:

1. Put a file called

   kickstart.rom

   in

   Kickstarts

   , which should be a kickstart 1.3 ROM
2. Extract a copy of Workbench 1.3 to

   Drives/Workbench1.3

3. Run

   winuae.exe

   (I included the version I'm using)
4. Load the

   File-name-truncation.uss

   save state

I also included a

Wiz-n-Liz.uss

so you check see it load the game under 6.0
But if you change the command line to 6.1 you can instead watch it crash

Hope I didn't break any rules for The Zone!