exxos's Atari, Amiga & retro forum

That’s exactly what I did, other than the .ini file.

I just copied the hda file to the SD card and then Hddriver recognises the SCSI drive at ID 1 as per the file name.

But now when I put the card in my windows machine I don’t see the image rather the individual drives are mounted.

I can definitely confirm I haven’t written the image using a tool. Just normal file copy.

All works fine in the BlueSCSI device so this is baffling me!

Cheers,

Simon

smoore100 wrote: 24 Jun 2024 10:00 That’s exactly what I did, other than the .ini file.

I just copied the hda file to the SD card and then Hddriver recognises the SCSI drive at ID 1 as per the file name.

But now when I put the card in my windows machine I don’t see the image rather the individual drives are mounted.

I can definitely confirm I haven’t written the image using a tool. Just normal file copy.

All works fine in the BlueSCSI device so this is baffling me!

Cheers,

Simon

It sounds to me like the HDA file is being automounted some how, because it's just not possible that all you're seeing is the partitions in the HDA file and not the root of the SD card with the HDA and ini file in it.

I'd suggest you check what your autoplay settings are in Windows.

Regardless you should still be able to see the root of the SD card in explorer.

Have a look here: Autoplay settings

Thanks, I took a look and Autoplay and it isn't enabled.

Tried it under Linux and same thing happens there too.

I'm wondering if I messed up when partitioning and somehow partitioned the entire SD card and not just the image?

smoore100 wrote: 24 Jun 2024 10:21 I'm wondering if I messed up when partitioning and somehow partitioned the entire SD card and not just the image?

That isn't possible since the BlueSCSI only exposes the image file to the Atari as a SCSI drive. So when the Atari partitions this 'drive' it only writes inside that image file. The Atari has no access to the file system of the SD card, as far as the Atari is concerned there is no such thing as the SD card, just the disk image file.

I unfortunately have no explanation for what you're describing. Certainly something very strange going on. The only explanation, as I've previously mentioned, is that you've accidentally imaged the SD card with the Atari drive on your PC. Other than that, it doesn't make any sense.

Steve wrote: 24 Jun 2024 10:39
That isn't possible since the BlueSCSI only exposes the image file to the Atari as a SCSI drive. So when the Atari partitions this 'drive' it only writes inside that image file. The Atari has no access to the file system of the SD card, as far as the Atari is concerned there is no such thing as the SD card, just the disk image file.

Yes that makes sense to me, so the image file must be on the card otherwise HDDriver wouldn't even see it at the correct SCSI ID?

That's correct. The BlueSCSI firmware scans the SD card for properly named image files, then depending on how you name it, it then assigns that image file as a drive with a SCSI ID to the Atari. Anything the Atari writes, gets written to that particular image file only.

I think I need to start from scratch again, and keep a clear record of what I do in case it happens again.

Will lose a couple of hours of Mint install time I did last night, but it'll hero me learn Mint better anyway!

Thanks,

Simon

smoore100 wrote: 24 Jun 2024 10:21 Thanks, I took a look and Autoplay and it isn't enabled.

Tried it under Linux and same thing happens there too.

I'm wondering if I messed up when partitioning and somehow partitioned the entire SD card and not just the image?

If Autoplay is off and the same thing happens under Linux then the likely issue is you formatted the SD card and not the image. Not sure how, as @Steve said, the SD card filesystem just isn't exposed for use, it's only accessible by the BlueSCSI device.

I probably did something wrong when I formatted the RAW partition using the Mint tools

smoore100 wrote: 24 Jun 2024 11:34 I probably did something wrong when I formatted the RAW partition using the Mint tools

I still don't know how though. How are you creating the image file? There should be no way to access the SD card via the BlueSCSI, only the HDA file that is presented as a disk.

I'd suggest you start again.

Create a blank HDA file of the size you want.

Copy that file to the SD card and create your ini file.

Attach the BlueSCSI to your machine (What are you using, a Falcon, a TT, something else?) boot up and then run the HDDRIVER installer to partition your HDA file and install the driver to the first partition.

That's it, all you need to boot to the first HDA image.