exxos's Atari, Amiga & retro forum

cathrynmataga wrote: 11 May 2025 22:10 I tried exactly that, the 0.2.0 version, and I also went back to the 'Atari modified version' -- what's weird is when I copy the whole thing to a directory in C:\ and run it, I just get random errors, eventually, after copying a few files and things. It's just random, sometimes it doesn't start, sometimes it does. Sometimes I see errors using cp. Sometimes it works enough to make me think I've solved it, but then it goes bad again eventually. I think maybe if I run it completely from physical floppy, it works, but not sure.

weird. I use it almost daily from hard drive without any major problems. Saying that, it's far from perfect and (for me at least) I'd definitely put it in the 'good enough' category. There definitely are bugs in there that I work around. I never saw the benefit of going too crazy fixing it. I assumed only I was using it and I never bother with the built in emacs :D

What version of TOS are you using and what disk driver? I might take a look.

Do you have any specific details of what/when it goes wrong?

I have TOS 1.06, and I've tried this two ways, once a hard disk with ACSI2STM Gemdos, and an on other with ACSI2STM formatted wit PPera 1.03 with a single 512MB ACSI disk. I can put little time into documenting how exactly this is going wrong now that I know someone out there has gotten this working and is actually willing to read this.

I have that directory copied to C:\APPS\GULAN and I start from emucon2 just so I can read the message. From TOS it does the same thing but flashes by too fast to read.
I removed Sidecartridge, so I only have ASCSI2STM with ACSI formatted drive. (to reduce variables)

And when I start it I see a message
"Fatal Error: insufficient memory
Hint: either reduce stack size using the 'stack' command (not recomended)
or increase TPA_INITIALMEM value in mint.cnf.
error code 65535

I put 4MB of RAM in this STE, and it did pass memory tests on the diagnostic cart.

What's weird is I have gulam.ttp located on my A: stock Atari floppy drive, and it loads from that fine, even after seeing failure message trying to load from C: I can manipulate files on the floppy disk fine.

To me, it's acting like something in gulam is confusing my hard disk drivers, but I have no insight beyond that.

cathrynmataga wrote: 12 May 2025 01:08 To me, it's acting like something in gulam is confusing my hard disk drivers, but I have no insight beyond that.

Thanks. I'll take a look. That message looks like something from libcmini/mintlib (I can't remember which library I built it with) so hopefully I can grep for it and trace it back.

Hi @cathrynmataga,
Does this version work for you? It's the version I have installed. It's been a while since I compiled it but I suspect that this version was compiled with Pure-C and the version in github with gcc in which case I need to fix the build.

Thanks for trying, but this is exactly the same version I've been running. I pull the TTP off of the hard drive and did a diff against this.

And I'm not sure what happened, but now it's settled on a 'different kind of broken' -- it launches now and I get to the command line. But cp test.txt test1.txt returns error code -33, but only hard drives. I can copy files floppy to floppy fine.

I'm afraid for me, there's just something random going on. It's not consistent.

cathrynmataga wrote: 13 May 2025 04:20 Thanks for trying, but this is exactly the same version I've been running. I pull the TTP off of the hard drive and did a diff against this.

And I'm not sure what happened, but now it's settled on a 'different kind of broken' -- it launches now and I get to the command line. But cp test.txt test1.txt returns error code -33, but only hard drives. I can copy files floppy to floppy fine.

I'm afraid for me, there's just something random going on. It's not consistent.

Thanks for trying that. I tried it on TOS 1.06 but with HDDRIVER and it worked fine. The original error indicated that there wasn't enough memory left to run, so either the program header was corrupt or something that ran before it hadn't released memory back to the pool.

I did initially wonder if it was GEMDOS related but the fact that it doesn't work with PP drivers sinks that idea. I'll maybe have to set up an ACSI2STM/PP driver environment at some point. I just can't replicate it at the moment.

I thought for a bit that PPERA+ACSI formatted would be the solution. But no. For me, it behaves about the same, gemdrive or ppera.

Really, I do get it. I'm still fiddling with the Atari ST gadgets I've bought, but I may pick up an UltraSatan some time too -- see what happens.

Oh oh oh, I figured it out. It was Gemdrive after all. This was PPera driver confusion by me. (I think in old days I had Atari drivers.) What happened was I paid Mr. PPera, I got the drivers, I stuck a SD card in and I formatted, and ran the install app, but I didn't notice that it never showed the install dialog on the install. I rebooted the Atari and it just worked -- but it was formatted in ACSI 16 mode, but running in Gemdrive mode. It just ran, so I figured it was okay, but it wasn't.
So, I soldered in the jumper for the 'strict mode option'. And with strict mode set, I ran the ppera tools, my volumes were all still there, so I ran the option to install the boot sector stuff, rebooted, and now gulam starts, it finds its batch file and just works.
Thanks for dealing with my 'been away from Atari for 20+ years confusion'. (Though I have been running hard disks from MisterFPA)
I may make another go at getting NDVI running, as all that stuff was acting weird too.

cathrynmataga wrote: 18 May 2025 06:33 Oh oh oh, I figured it out. It was Gemdrive after all. This was PPera driver confusion by me. (I think in old days I had Atari drivers.) What happened was I paid Mr. PPera, I got the drivers, I stuck a SD card in and I formatted, and ran the install app, but I didn't notice that it never showed the install dialog on the install. I rebooted the Atari and it just worked -- but it was formatted in ACSI 16 mode, but running in Gemdrive mode. It just ran, so I figured it was okay, but it wasn't.
So, I soldered in the jumper for the 'strict mode option'. And with strict mode set, I ran the ppera tools, my volumes were all still there, so I ran the option to install the boot sector stuff, rebooted, and now gulam starts, it finds its batch file and just works.
Thanks for dealing with my 'been away from Atari for 20+ years confusion'. (Though I have been running hard disks from MisterFPA)
I may make another go at getting NDVI running, as all that stuff was acting weird too.

No problem. It's good to know that it's working :D

And, posting, not much to say. Just trying to get my hour in to make sure my IP doesn't get banned. (I did recent switch IP addresses)