Hi,
I created an HFE v3 image file using the version 2.16.10.1 of the floppy emulator tools. IBM MFM track type, 40 track, 18 sectors per track/256 bytes per sector. This is for use on a TRS-80 Model 4.
The HxC gives a "bad file" error when I select the image. I was able to create a HFE v2 image with the same parameters as above and the HxC is able to use it.
Is there an option on the HxC I need to specify? I'm running latest beta firmware 1.8.8.1. I had previously tried the above using floppy emulator tools 2.15.2.3 and firmware 1.8.2.40 with the same result. Or is HFE v3 just not supported. Same issue for the HFE Streams version as well.
On the TRS-80 I'm finding there seems to be a problem with imaging some self-booting games disks. I think it is related to tracks with mixed density designed for booting on either a Model 1 or a Model 3/4. Typically track 0, sector 0 will be single density to support the Mod 1 boot sector and track 0 sector 1 will be double density for 3/4 boot sector. Typically, the remainder of the disks will be single density but for a Model 1 with a double density board installed the entire disk could be double density with just track 0 sector 0 being single. I'm actually wondering how well the HxC/HFE works on a Model 1 since running the double density upgrade is very common and every Model 1 DD boot disk will have a single density track 0 sector 0. I need to get my Model 1 up and running and test this out.
HFE v3 - "bad file"
Re: HFE v3 - "bad file"
As I posted in response to a separate question I had, I did find a work around on a Gotek (I had to buy a Gotek to figure this out first, though, haha).
I can copy these mixed density games disks to an HFE v1 file on the Gotek and get a good image which will boot.
The image can be moved over to a Lotharek HxC and will boot fine as well so it is some sort of quirk writing to the HxC causing this.
I can copy these mixed density games disks to an HFE v1 file on the Gotek and get a good image which will boot.
The image can be moved over to a Lotharek HxC and will boot fine as well so it is some sort of quirk writing to the HxC causing this.