nfg.forums

Quote from: aotta on February 12, 2025, 09:06:01 AMSo, you have both internal and external drive mounted at bootup? so try simply removing external floppies...

Ohh I'm not sure where those C: and D: floppy drives come from, I only have the floppy drives at A: and B: and the external ZuluSCSI drive.

If there's an easy way of removing the "ghost floppy drives" at C: and D: happy to try that! (That way I can use the HDD image "as is" moving forward)

I'll give a quick rundown and if you need more help let me know and I'll run through it with some screenshots.

1. The easiest way for me to make a SASI image is using XM6-Pro 68k - Theres an option in the menu to created a fixed SASI disk. Use that option and make one thats 40MB total in size.

2. Boot into Human68k and run format, making 1 38MB partition as your system and then another 2mb empty partition as your last one.

3. remove disk and reboot machine with your newly made image, or move files to it via editdisk or other means.

Quote from: taarriag on February 12, 2025, 04:58:02 AMWhen I looked into the default assigned letters (using DRIVE with no arguments), it identified A: to D: as floppy drives, then E: as the first SCSI drive.

So, you have both internal and external drive mounted at bootup? so try simply removing external floppies...

Here's the deal- I'm looking to create a proper SASI HDD image that can boot Human68k system and run some drivers and diagnostic software and some small games, somewhat like incrediblehark's SXSI HDD but for SASI machines so these early SASI machines can boot it directly right out of the box. ArdSCSIno can boot SASI images using this protocol btw. There is a limitation of 40MB maximum tho. There is 1 thing I want to recreate but I have no idea how- Human68k system has to read FDD drives 0 and 1 and otherwise it refuses to boot unfortunately so technically FDD drives need to be connected even though the system boots from HDD which sounds crazy and very limiting to me. However there is a hack in the SXSI HDD image where there is a free 2MB partition that acts like a hack so that image can boot without FDD drives present or something along these lines. How do you apply the same hack for a custom SASI HDD image? This is the only thing I have absolutely no idea how to achieve but I believe I can do the rest like filling the HDD with programs and drivers and so on. Please help. Thanks

UPDATE: link to the image:
https://drive.google.com/file/d/13F_iCj9OMuhK8PherqYWMolGYimlPxlg/view?usp=sharing

IIRC it didn't let me change that option under switch.x (but I can double check when I get home).

There was an option for setting the maximum number of HDDs which I set to 0 thinking it may do the trick, but it still assigned E: to SCSI drive 1.

When I looked into the default assigned letters (using DRIVE with no arguments), it identified A: to D: as floppy drives, then E: as the first SCSI drive.

ah okay, no worries... what model exactly you got, ping me if you need anything.

Quote from: amazin on February 12, 2025, 02:02:45 AMHey @Clueless I'm in the UK too, I could send you one of my boards, as I have extras... Just need to find where I put them, but I certainly have a spare.

Do you wanna share 1/5 of the costs?

Cheers

Thank you for the kind offer @amazin, I got this message too late, I was too keen to buy as my machines on it's way to me, and I want to hit the ground running

If you've any other spare parts, or information on where to get the essentials a new FM Towns 2 owner might need I'd really appreciate that also (e.g: FDD drive belts, anywhere selling the ODE's, etc).

Thanks again @amazin

Hey @Clueless I'm in the UK too, I could send you one of my boards, as I have extras... Just need to find where I put them, but I certainly have a spare.

Do you wanna share 1/5 of the costs?

Cheers

I'm about to get PCB way to make this for me. I've not used them before but looks like the minimum order size it 5... Anyone in the UK need one of these?

@taarriag how many sasi drive did you assign to sasi driver in switch.x config? Couldn't it be the issue in starting assigning scsi drives to letter E?