Ms Mad LemonTo all fellow Amiga users out there, which kickstart/workbench version do you use? Please answer on the poll linked here:
http://youtube.com/post/Ugkxx4dmGmvl0lSFsoRPpWrJN0w8ARVescdP?si=XJKzIXbiX8LRtK4y
woodycool@MsMadLemon thanks for sharing - although, I'm starting to get the idea that there's not a lot of interest in 1.2/1.3 these days
That bug in my disk mag that only gets exhibited on 1.2/1.3 might be less of a problem than I think it is
Charlie Balogh@woodycool @MsMadLemon Not many (in relative terms) people use a full-fledged, expanded 1.x system, with hard disk & stuff. Those systems are mostly just stick the floppy in, and go. (Note: I do have an A590 disk controller for my A500, so I know this isn't always the case. But in general.)
But (almost) anything with network, more advanced HDD/SCSI setup, etc. needs at least 2.x+, most likely 3.x. So depends on what your target audience/use case is.
@chainq @MsMadLemon well, I'm working on something, but it's targeted to 1.3 and boots from floppy (although, can easily be run from HD by copying all the files to a single drawer/folder)
I do have an A590 on my A500 though, and do have a nice 1.3 HD setup (well, it's got SCSI2SD in it as the original drive died a death years ago)
@woodycool @MsMadLemon Yeah, my A590 has a SCSI2SD v5 too. It's just the way it goes these days...
I have _some_ experience targeting systems with different OS versions, so now I'm intrigued what your bug might be... 😅
@chainq @MsMadLemon ok, so I'm writing a disk mag, and I get different behaviour under 1.x than I do under any other OS - on a 1.x machine, as the contents page grows, the disk mag gets to a stage where after the intro graphics have displayed, the Amiga gets stuck in a loop reading from the floppy (or ADF) - this is even replicated in an emulator, so not just a real hardware problem - on a 2.x or 3.x machine, the problem doesn't exist
@chainq @MsMadLemon in an emulator, if you turn on the status line, you can see it's sticking reading the same two tracks over and over again .............. I think it's a bug between how Magnum Pro (the Disk Mag engine being used) and trackdisk.device work on a 1.3 machine
Magnum Pro is written in AMOS and I do have the source code, but, the code is spaghetti and I'm struggling to work out the problem
I moved all the content over to DMC instead last night, which doesn't fail like this, but...
@chainq @MsMadLemon under DMC, the music plays for about a minute and then starts going crazy making screeching noises and sounding corrupt (but doesn't do this on Magnum Pro)
I'm leaning towards having to write my own Disk Mag engine now, as the two biggest well known ones that many used back in the day have problems
@woodycool @MsMadLemon Writing another diskmag engine sounds like a major untertaking just to solve this...
From a distance, both cases smell like some memory trashing issue. Either you run out of RAM, or there's a piece of content that is processed in a way that trips over on KS 1.3? (Example: some newer IFF conversion tools might create things that these older software dislike and mishandle.)
@chainq @MsMadLemon I never thought about it like that, but that's a good point - RAM wise, I don't see why it'd run out of RAM on 1.3 and not 2.0 or above (when tested with the same 1MB config on both) - but, what I didn't mention is this .............. under Magnum Pro (the one with the 1.3 problem), if I leave it in this "stuck loop" for a really long time (like 30 minutes or something daft like that), it will actually load.
Theres defo something tripping it up, other diskmags in Magnum work
@chainq @MsMadLemon as for DMC corrupting the audio on the music file, I have no idea ............ I have the AMOS source for Magnum Pro, but there's no source anywhere in sight for DMC, so I cannot look at it's routine to how it handles the music.
@chainq @MsMadLemon my other option is, I say "tough, you need Kickstart 2.0 or later" but that feels like a cop out ........ but this is the reason behind the poll, I can work out how many people still use 1.3
Regionales Retro-Rechenzentrum@MsMadLemon Kickstart 1.3 a lot, but also 2.x and 3.x.
PastaThief@MsMadLemon I hope you're interested in folks who only emulate! I answered from the perspectiva.
@PastaThief This is for a diskmag project a friend is doing. Someone who is emulating can switch Kickstart ROM as they need to. Unless they have a switcher, people with real hardware cannot easily switch their kickstart ROM. So it's more from that angle.
I'm not anti-emulation if that's what you're wondering.
I'm not anti-emulation if that's what you're wondering.