gollumer Posted March 19, 2021 Share Posted March 19, 2021 I have an UltraSatan with a formatted/partitioned SD card. I connected it to my Mega STe. During bootup, it shows 5 partitions. C is 14MB, the rest are all 248MB. I get the desktop, with C drive showing. I highlight C, then install devices. It then shows the other partitions. But when I try to Save Desktop, it tells me that drive C does not have enough room for this operation. (Note: all partitions are currently empty...) What am I missing? Quote Link to comment Share on other sites More sharing options...
TGB1718 Posted March 19, 2021 Share Posted March 19, 2021 Have the partitions been formatted ? I don't used the HDD driver you are using, so not sure if that's done as part of the partition creation process Quote Link to comment Share on other sites More sharing options...
ParanoidLittleMan Posted March 19, 2021 Share Posted March 19, 2021 Interesting. Most likely the reason is low quality SD card. And what to expect from someone using illegally SW, not reading instructions, and actually using wrong version of driver. What is capacity of that card printed on it ? Asking because there are no cards with exactly 1 GB capacity. It is written only because Basic ACSI has max 1GB accessible, and this driver has capacity test what goes up to that size, if card is bigger, it will be not shown. Then, first partition can be much bigger with this driver (512 MB). For UltraSatan there is special driver,what has letters hs after version number, supports hot swap of cards, very large SD cards ... You missing decent seller. Quote Link to comment Share on other sites More sharing options...
+DarkLord Posted March 19, 2021 Share Posted March 19, 2021 What he said. I've had the best luck with SanDisk brand name cards. Just my experience, for what it's worth. Quote Link to comment Share on other sites More sharing options...
gollumer Posted March 19, 2021 Author Share Posted March 19, 2021 (edited) Ok, I overwrote the SD card with PP's 15MB.img. It showed a 14MB partition, and booted into the desktop with both PP13U.PRG and USAB101.TOS listed. I launched PP13U, selected ACSI 0, and started adding partition info. I then selected "PARTIT. and INIT all". It seemed to finish fine (the green pie chart now showed a nearly full pie....). I then launched USAB101.TOS, typed 0, then I, and got an error message "Not DOS part. disk". I tried rebooting, but now get 4 bombs... I'm going to try with a different SD card and see what happens. Edited March 19, 2021 by gollumer Quote Link to comment Share on other sites More sharing options...
gollumer Posted March 19, 2021 Author Share Posted March 19, 2021 Update: Tried it with a different SD card (16GB SanDisk). Same issue. "Not DOS part, disk". I don't get the bombs anymore, but the SD card is unusable. I've re-flashed the 15MB.img several times, and each time end up with the same result. Quote Link to comment Share on other sites More sharing options...
gollumer Posted March 20, 2021 Author Share Posted March 20, 2021 UPDATE 2: This morning I tried with a different computer (a 520ST with TOS 1.02). It worked! Because it's TOS 1.02, I had to partition each drive as 255...but it worked. So, I'm thinking there's something wrong with the Mega STe. Any ideas what it might be? Could it be a bad DMA chip? Quote Link to comment Share on other sites More sharing options...
+DarkLord Posted March 20, 2021 Share Posted March 20, 2021 (edited) Just so it's out there, is this an internal or external Ultrasatan? Do you have another ST besides the Mega STe to try this on? Is the US the only device on the ASCI chain? Thanks. PS Wow - literally your last post must have came in seconds before this one... Edited March 20, 2021 by DarkLord Updated.... Quote Link to comment Share on other sites More sharing options...
Cubeast Posted March 20, 2021 Share Posted March 20, 2021 6 hours ago, gollumer said: UPDATE 2: This morning I tried with a different computer (a 520ST with TOS 1.02). It worked! Because it's TOS 1.02, I had to partition each drive as 255...but it worked. So, I'm thinking there's something wrong with the Mega STe. Any ideas what it might be? Could it be a bad DMA chip? Your thinking is most likely wrong. I would hope that your Mega STE is using a different TOS version than that which is displayed by the software in your screen shots....but then the guy who's software you are using pointed that out to you already. Quote Link to comment Share on other sites More sharing options...
+DarkLord Posted March 21, 2021 Share Posted March 21, 2021 Wonder if he's got a Mega ST instead of Mega STe...? Quote Link to comment Share on other sites More sharing options...
gollumer Posted March 21, 2021 Author Share Posted March 21, 2021 17 hours ago, Cubeast said: Your thinking is most likely wrong. I would hope that your Mega STE is using a different TOS version than that which is displayed by the software in your screen shots....but then the guy who's software you are using pointed that out to you already. There is no TOS version displayed in the screenshots. The reason the partitions were kept small (initially) is that I have other, older, STs with lower TOS versions so I wanted one card to be compatible with all of them. But when it wasn't working (couldn't save the desktop), I re-partitioned it with larger drives. As I pointed out in my later post, I was able to successfully partition, initialize, and save desktop on my 520ST with an older TOS version. (The STe has TOS 2.06) So, again, it seems the issue is with the STe. It won't write to the card, and doesn't partition or initialize properly. Quote Link to comment Share on other sites More sharing options...
gollumer Posted March 21, 2021 Author Share Posted March 21, 2021 15 hours ago, DarkLord said: Wonder if he's got a Mega ST instead of Mega STe...? No, it's a Mega STe. (Same case as the TT030) Quote Link to comment Share on other sites More sharing options...
+DarkLord Posted March 21, 2021 Share Posted March 21, 2021 (edited) 2 hours ago, gollumer said: No, it's a Mega STe. (Same case as the TT030) Oh, okay - thanks! So about the other questions I posed: Just so it's out there, is this an internal or external Ultrasatan? (assuming the Mega STe has a working internal hard drive?) Is the US the only device on the ASCI chain? Edited March 21, 2021 by DarkLord Updated.... Quote Link to comment Share on other sites More sharing options...
snarkdluG Posted March 21, 2021 Share Posted March 21, 2021 Without an internal SCSI card D0-D7 is not connected so the external ACSI will not work. You can also try changing the ID of US to something else then 0 with the config tool from Lotharek site. Quote Link to comment Share on other sites More sharing options...
gollumer Posted March 21, 2021 Author Share Posted March 21, 2021 3 hours ago, DarkLord said: Oh, okay - thanks! So about the other questions I posed: Just so it's out there, is this an internal or external Ultrasatan? (assuming the Mega STe has a working internal hard drive?) Is the US the only device on the ASCI chain? External. The internal drive isn't working. This is the only device connected. Works fine on the 520ST, but not the STe. Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.