Menu

Steem Errors with NeoDesk and Geneva

2024-05-23
2025-04-12
  • Old Guy Geek

    Old Guy Geek - 2024-05-23

    Hi,

    I've been preparing a tutorial to show how to install/use NeoDesk4 with Geneva. As with all my YouTube tutorials, I use Steem to demonstrate. Steem has been invaluable in running various ST software. But this time, after weeks of testing I'm stumped.

    Rather than a boot manager, I run Steem using a separate folder for each type of use. For example, I have a C: drive folder called CNeoDesk4. In that folder I put all the usual directories and files needed to boot from that drive. Similarly for other uses besides NeoDesk dedicated folders have worked flawlessly.

    But I recently discovered that Dan Wilga of Gribnif Software has updated NeoDesk to version 4.06 and released it into the wild. He has also released Geneva.

    I successfully installed it using the install programs provided. Later, during troubleshooting, I also successfully installed it manually. I have installed it both with the ACCs in an ACC folder or with them in the root. Both configurations run, but I have encountered two problems that have proved insurmountable even after many hours of testing.

    To be clear, I prefer Steem over Hatari, but to test if the problems persisted, I used the same files and system configuration in Hatari. Everything works perfectly in Hatari. The only difference is in Hatari I have to set the Atari's memory to at least 8MB in order for it to load. Even if I do the same in Steem, using either the 12MB or 14MB setting, these problems persist.

    Problem 1: Not all ACC load. I have attached screenshots of both the Hatari and Steem menus showing which accessories load. As you will see, Hatari loads all of them while Steem only load a couple. Also there are no error messages that anything went wrong.

    Problem 2: When Steem boots and loads Geneva and NeoDesk4, there are no apparent problems until you try and access one of the hard drive icons. The system pauses for a bit and then gives a message that Drive A: is not responding. It does this for either of the GEMDOS drives that I am using. In addition, it also does it when you try and double click on an interior folder in one of those drives. Same pause as it tries to access the A: drive and then the message. Once you dismiss it, it continues and opens the directory you are trying to access.

    I have attached a screenshots of Steem's A: drive error accessing the root of the hard drive or any subordinate folder.

    Hopefully, I'm just having a bad week and this old brain is overlooking something simple. Any help you could provide would be greatly appreciated.

    Thanks,

    YouTube
    theAtariGeek (atari stuff)
    OldGuyGeek (windows stuff)

     
  • STeven

    STeven - 2024-05-25

    Hi,
    Thx for the report. It's not you, it's Steem.
    You failed to provide useful links but I found the software.
    Seems to be 2 different bugs indeed. It's surprising this problem didn't come up before (who uses Steem SSE, right?)
    Please try the new beta R20, those problems are fixed (but maybe there are others now).

    https://sourceforge.net/projects/steemsse/files/Steem%20SSE%20Beta/Steem_SSE_Beta_420_R20.7z/download

     
  • Old Guy Geek

    Old Guy Geek - 2024-05-29

    Just saw your response. Took only a minute or two to copy over my .ini files and BAM all the accessories worked AND no A: drive prompt!

    You are the man!!!!!!

     
  • Ryan Gary

    Ryan Gary - 2025-04-12

    Ah, the classic compatibility struggles—like trying to mix ketchup and ice cream 😅 I’ve run into similar issues when using Geneva with NeoDesk. Feels like the software equivalent of ordering In-N-Out and getting McDonald's by mistake. Anyone found a tasty fix for this combo yet?

     

    Last edit: Ryan Gary 2025-04-12

Log in to post a comment.

MongoDB Logo MongoDB