How to read 5 1/4" & 3 1/2" Floppies into Software for .HFE

General discussion forum - for all that doesn't fit in any other category.
Post Reply
ldkraemer
Posts: 51
Joined: Thu Feb 28, 2013 3:47 am

How to read 5 1/4" & 3 1/2" Floppies into Software for .HFE

Post by ldkraemer »

I'm new to the HxC Hardware and Software. I'm interested in the Cased SLIM for making a Drive that will support my
Kaypro II, Ampro Little Board, Radio Shack Model 1, 3, 4 all of which will be mostly running CP/M.

I've currently been running some CP/M Emulators, but I'd like to keep the Original Hardware functional and use the SLIM.

I've got several stacks of OLD 5 1/4" floppies of various formats, CP/M, LDOS, TRSDOS, and NEWDOS.

My question is how do I go about getting these Floppies read into the HxC software? I've downloaded the two software
packages, floppyimage_convert.EXE and HxCFloppy_Emulator.EXE. I finally figured out that floppyimage_convert.EXE
must be run from the command line, and HxCFloppy_Emulator.EXE is a Windows Program.

If I connect a 5 1/4" drive OR a 3 1/2" Drive to my Windows XP Machine how do I create the *.HFE Images that can boot,
and run from the SLIM when it is inserted into the Kaypro II? I've read on the forum to start the process before the SLIM arrives,
but no information on how to get the process started.

I need a bit more detail on how to make the tranfers.

I've previously used a Catweasel Board, with Linux, to read several CP/M Floppies and made .DMK images of those.

If there is a detailed document on how to use the software, or just a document file it would be a big help.

Also, is the Conversion software available for Linux? WHERE? I typically run Ubuntu, Debian, Slackware, or Linux Mint.

Thanks.

Larry

Jeff
Site Admin
Posts: 8092
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: How to read 5 1/4" & 3 1/2" Floppies into Software for .

Post by Jeff »

I have one question : did you received my emails ?

ldkraemer
Posts: 51
Joined: Thu Feb 28, 2013 3:47 am

Re: How to read 5 1/4" & 3 1/2" Floppies into Software for .

Post by ldkraemer »

Yes Sir:
I received the following answers to my emails, but I didn't get the necessary information on which software to execute:
Hi,

>Dear Sir:
>I'm wanting to use this Floppy Emulator on the following machines:
>1. Kaypro II (running CP/M)
Just had a look to the schematic : No problem at all for me.

>2. Radio Shack TRS-80 Model 4 (running CP/M)

Already working !
>3. Ampro Little Board (Z80) (running CP/M)
Just had a look to the schematic : ok for me.

>4. Brother Embroidery Machine
Which one ?

>Will I be able to configure your SLIM to work with the Radio Shack Model 4?

Yes. Just use the software to convert JV1/JV3/DMK image to HFE.

>Do you have documentation on the DIP switch, that explains the configuration of the drive by the switches? I'd like to view that
>information before I purchase.
Attached a Draft !

>Also, when will the SLIM Cased Version be available?
Lotharek any comment ?

>I've downloaded the files to view, but most of your Documentation is for the Cased HXC Version with three buttons. When will your
>Documents be updated for the SLIM Version? I'd like a copy of those before purchase.

Most of the process is the same : you must generate HFE file image from image or disk and copy them to the sdcard.
Since the slim doesn't have (yet) lcd screen a new indexed mode allow you to change image with the button.

>Any other information you can supply would be helpful, like explaining how I would be able to boot up on a system disk (image) copied to your
>parition #4.

i don't understand well this point ?
and
Hi,

You can find the pinout into the user manual :
https://hxc2001.com/download/floppy_driv ... al_ENG.pdf

And in the Rev C schematic :

https://hxc2001.com/download/floppy_driv ... or_Kit.zip

>My problem is making the decision on the HXC SD Floppy Emulator Rev F or the Cased SLIM unit. Do you have a better suggestion than the Cased SLIM?

The slim version use a new and better design. the only drawback for the moment is the lack of lcd screen, but a firmware update will allow you to connect one on the i2c screen.
Unfortunately the answers didn't explain the process well enough, because my Floppy's could be any one of the following formats:
TRS-80 Model 4,4P Montezuma System 170K - SSDD 48 tpi 5.25"
TRS-80 Model 4,4P Montezuma Data 200K - SSDD 48 tpi 5.25"
TRS-80 Model 4,4P Montezuma System 350K - DSDD 48 tpi 5.25"
TRS-80 Model 4,4P Montezuma Data 400K - DSDD 48 tpi 5.25"
TRS-80 Model 4,4P Montezuma System 350K - SSDD 96 tpi 5.25"
TRS-80 Model 4,4P Montezuma Data 400K - SSDD 96 tpi 5.25"
TRS-80 Model 4,4P Montezuma System 710K - DSDD 96 tpi 5.25"
TRS-80 Model 4,4P Montezuma Data 800K - DSDD 96 tpi 5.25"
TRS-80 Model 4,4P Montezuma Extend System 190K - SSDD 48 tpi 5.25"
TRS-80 Model 4,4P Montezuma Extend System 390K - SSDD 48 tpi 5.25"
TRS-80 Model 4,4P Montezuma Extend System 390K - SSDD 96 tpi 5.25"
TRS-80 Model 4,4P Montezuma Extend System 790K - DSDD 96 tpi 5.25"
TRS-80 Model 4,4P Montezuma Super Data 220K - SSDD 48 tpi 5.25"
TRS-80 Model 4,4P Montezuma Super Data 440K - DSDD 48 tpi 5.25"
TRS-80 Model 4,4P Montezuma Super Data 440K - SSDD 96 tpi 5.25"
TRS-80 Model 4,4P Montezuma Super Data 880K - DSDD 96 tpi 5.25"
TRS-80 Model 4,4P Montezuma System 400K - SSDD 96 tpi 3.5"

So, I've executed both Software programs in XP, but I'm missing the steps of how I'm supposed to take one of my CP/M System Floppys, or Data Floppys, and read it from an IBM type Computer running Windows XP, using one of your software programs, to create a JV1/JV3/DMK file which somehow gets written as a .HFE file, which is used by your HxC SD Card SLIM Board.

It doesn't help that I'm out of State for a few Months, but when I get home, and have my hardwired Floppy's, I'm sure after several hours I'll figure it out on my own.

Larry

ldkraemer
Posts: 51
Joined: Thu Feb 28, 2013 3:47 am

Re: How to read 5 1/4" & 3 1/2" Floppies into Software for .

Post by ldkraemer »

I finally figured out how to load my *.DSK images that I had previously built with my Catweasel board.
I was thinking that the track Indicator on the bottom of the Window would advance as the file was read,
but that isn't the case.

The *.hfe files were built and I looked at the *.LOG files. Here is the LOG file for MMCPM231.DSK:

Code: Select all

DEBUG  : MFM 0A09 - 0029
DEBUG  : MFM 0B5F - 0029
DEBUG  : MFM 0CB5 - 0029
DEBUG  : MFM 0E0B - 0029
DEBUG  : MFM 0F61 - 0029
DEBUG  : MFM 10B7 - 0029
DEBUG  : MFM 120D - 0029
DEBUG  : MFM 1363 - 0029
DEBUG  : MFM 14B9 - 0029
DEBUG  : MFM 160F - 0029
DEBUG  : MFM 1765 - 0029
INFO 1 : Track 30 Side 0 Tracklen 6400 TTableOffset:0x0002ee10
ERROR  : ----------------------------
DEBUG  : MFM 00AF - 0029
DEBUG  : MFM 0205 - 0029
DEBUG  : MFM 035B - 0029
DEBUG  : MFM 04B1 - 0029
DEBUG  : MFM 0607 - 0029
DEBUG  : MFM 075D - 0029
DEBUG  : MFM 08B3 - 0029
DEBUG  : MFM 0A09 - 0029
DEBUG  : MFM 0B5F - 0029
DEBUG  : MFM 0CB5 - 0029
DEBUG  : MFM 0E0B - 0029
DEBUG  : MFM 0F61 - 0029
DEBUG  : MFM 10B7 - 0029
DEBUG  : MFM 120D - 0029
DEBUG  : MFM 1363 - 0029
DEBUG  : MFM 14B9 - 0029
DEBUG  : MFM 160F - 0029
DEBUG  : MFM 1765 - 0029
INFO 1 : Track 31 Side 0 Tracklen 6400 TTableOffset:0x00030710
ERROR  : ----------------------------
DEBUG  : MFM 00AF - 0029
DEBUG  : MFM 0205 - 0029
DEBUG  : MFM 035B - 0029
DEBUG  : MFM 04B1 - 0029
DEBUG  : MFM 0607 - 0029
DEBUG  : MFM 075D - 0029
DEBUG  : MFM 08B3 - 0029
DEBUG  : MFM 0A09 - 0029
DEBUG  : MFM 0B5F - 0029
DEBUG  : MFM 0CB5 - 0029
DEBUG  : MFM 0E0B - 0029
DEBUG  : MFM 0F61 - 0029
DEBUG  : MFM 10B7 - 0029
DEBUG  : MFM 120D - 0029
DEBUG  : MFM 1363 - 0029
DEBUG  : MFM 14B9 - 0029
DEBUG  : MFM 160F - 0029
DEBUG  : MFM 1765 - 0029
INFO 1 : Track 32 Side 0 Tracklen 6400 TTableOffset:0x00032010
ERROR  : ----------------------------
DEBUG  : MFM 00AF - 0029
DEBUG  : MFM 0205 - 0029
DEBUG  : MFM 035B - 0029
DEBUG  : MFM 04B1 - 0029
DEBUG  : MFM 0607 - 0029
DEBUG  : MFM 075D - 0029
DEBUG  : MFM 08B3 - 0029
DEBUG  : MFM 0A09 - 0029
DEBUG  : MFM 0B5F - 0029
DEBUG  : MFM 0CB5 - 0029
DEBUG  : MFM 0E0B - 0029
DEBUG  : MFM 0F61 - 0029
DEBUG  : MFM 10B7 - 0029
DEBUG  : MFM 120D - 0029
DEBUG  : MFM 1363 - 0029
DEBUG  : MFM 14B9 - 0029
DEBUG  : MFM 160F - 0029
DEBUG  : MFM 1765 - 0029
INFO 1 : Track 33 Side 0 Tracklen 6400 TTableOffset:0x00033910
ERROR  : ----------------------------
DEBUG  : MFM 00AF - 0029
DEBUG  : MFM 0205 - 0029
DEBUG  : MFM 035B - 0029
DEBUG  : MFM 04B1 - 0029
DEBUG  : MFM 0607 - 0029
DEBUG  : MFM 075D - 0029
DEBUG  : MFM 08B3 - 0029
DEBUG  : MFM 0A09 - 0029
DEBUG  : MFM 0B5F - 0029
DEBUG  : MFM 0CB5 - 0029
DEBUG  : MFM 0E0B - 0029
DEBUG  : MFM 0F61 - 0029
DEBUG  : MFM 10B7 - 0029
DEBUG  : MFM 120D - 0029
DEBUG  : MFM 1363 - 0029
DEBUG  : MFM 14B9 - 0029
DEBUG  : MFM 160F - 0029
DEBUG  : MFM 1765 - 0029
INFO 1 : Track 34 Side 0 Tracklen 6400 TTableOffset:0x00035210
ERROR  : ----------------------------
DEBUG  : MFM 00AF - 0029
DEBUG  : MFM 0205 - 0029
DEBUG  : MFM 035B - 0029
DEBUG  : MFM 04B1 - 0029
DEBUG  : MFM 0607 - 0029
DEBUG  : MFM 075D - 0029
DEBUG  : MFM 08B3 - 0029
DEBUG  : MFM 0A09 - 0029
DEBUG  : MFM 0B5F - 0029
DEBUG  : MFM 0CB5 - 0029
DEBUG  : MFM 0E0B - 0029
DEBUG  : MFM 0F61 - 0029
DEBUG  : MFM 10B7 - 0029
DEBUG  : MFM 120D - 0029
DEBUG  : MFM 1363 - 0029
DEBUG  : MFM 14B9 - 0029
DEBUG  : MFM 160F - 0029
DEBUG  : MFM 1765 - 0029
INFO 1 : Track 35 Side 0 Tracklen 6400 TTableOffset:0x00036b10
ERROR  : ----------------------------
DEBUG  : MFM 00AF - 0029
DEBUG  : MFM 0205 - 0029
DEBUG  : MFM 035B - 0029
DEBUG  : MFM 04B1 - 0029
DEBUG  : MFM 0607 - 0029
DEBUG  : MFM 075D - 0029
DEBUG  : MFM 08B3 - 0029
DEBUG  : MFM 0A09 - 0029
DEBUG  : MFM 0B5F - 0029
DEBUG  : MFM 0CB5 - 0029
DEBUG  : MFM 0E0B - 0029
DEBUG  : MFM 0F61 - 0029
DEBUG  : MFM 10B7 - 0029
DEBUG  : MFM 120D - 0029
DEBUG  : MFM 1363 - 0029
DEBUG  : MFM 14B9 - 0029
DEBUG  : MFM 160F - 0029
DEBUG  : MFM 1765 - 0029
INFO 1 : Track 36 Side 0 Tracklen 6400 TTableOffset:0x00038410
ERROR  : ----------------------------
DEBUG  : MFM 00AF - 0029
DEBUG  : MFM 0205 - 0029
DEBUG  : MFM 035B - 0029
DEBUG  : MFM 04B1 - 0029
DEBUG  : MFM 0607 - 0029
DEBUG  : MFM 075D - 0029
DEBUG  : MFM 08B3 - 0029
DEBUG  : MFM 0A09 - 0029
DEBUG  : MFM 0B5F - 0029
DEBUG  : MFM 0CB5 - 0029
DEBUG  : MFM 0E0B - 0029
DEBUG  : MFM 0F61 - 0029
DEBUG  : MFM 10B7 - 0029
DEBUG  : MFM 120D - 0029
DEBUG  : MFM 1363 - 0029
DEBUG  : MFM 14B9 - 0029
DEBUG  : MFM 160F - 0029
DEBUG  : MFM 1765 - 0029
INFO 1 : Track 37 Side 0 Tracklen 6400 TTableOffset:0x00039d10
ERROR  : ----------------------------
DEBUG  : MFM 00AF - 0029
DEBUG  : MFM 0205 - 0029
DEBUG  : MFM 035B - 0029
DEBUG  : MFM 04B1 - 0029
DEBUG  : MFM 0607 - 0029
DEBUG  : MFM 075D - 0029
DEBUG  : MFM 08B3 - 0029
DEBUG  : MFM 0A09 - 0029
DEBUG  : MFM 0B5F - 0029
DEBUG  : MFM 0CB5 - 0029
DEBUG  : MFM 0E0B - 0029
DEBUG  : MFM 0F61 - 0029
DEBUG  : MFM 10B7 - 0029
DEBUG  : MFM 120D - 0029
DEBUG  : MFM 1363 - 0029
DEBUG  : MFM 14B9 - 0029
DEBUG  : MFM 160F - 0029
DEBUG  : MFM 1765 - 0029
INFO 1 : Track 38 Side 0 Tracklen 6400 TTableOffset:0x0003b610
ERROR  : ----------------------------
DEBUG  : MFM 00AF - 0029
DEBUG  : MFM 0205 - 0029
DEBUG  : MFM 035B - 0029
DEBUG  : MFM 04B1 - 0029
DEBUG  : MFM 0607 - 0029
DEBUG  : MFM 075D - 0029
DEBUG  : MFM 08B3 - 0029
DEBUG  : MFM 0A09 - 0029
DEBUG  : MFM 0B5F - 0029
DEBUG  : MFM 0CB5 - 0029
DEBUG  : MFM 0E0B - 0029
DEBUG  : MFM 0F61 - 0029
DEBUG  : MFM 10B7 - 0029
DEBUG  : MFM 120D - 0029
DEBUG  : MFM 1363 - 0029
DEBUG  : MFM 14B9 - 0029
DEBUG  : MFM 160F - 0029
DEBUG  : MFM 1765 - 0029
INFO 1 : Track 39 Side 0 Tracklen 6400 TTableOffset:0x0003cf10
ERROR  : ----------------------------
DEBUG  : MFM 00AF - 0029
DEBUG  : MFM 0205 - 0029
DEBUG  : MFM 035B - 0029
DEBUG  : MFM 04B1 - 0029
DEBUG  : MFM 0607 - 0029
DEBUG  : MFM 075D - 0029
DEBUG  : MFM 08B3 - 0029
DEBUG  : MFM 0A09 - 0029
DEBUG  : MFM 0B5F - 0029
DEBUG  : MFM 0CB5 - 0029
DEBUG  : MFM 0E0B - 0029
DEBUG  : MFM 0F61 - 0029
DEBUG  : MFM 10B7 - 0029
DEBUG  : MFM 120D - 0029
DEBUG  : MFM 1363 - 0029
DEBUG  : MFM 14B9 - 0029
DEBUG  : MFM 160F - 0029
DEBUG  : MFM 1765 - 0029
INFO 1 : track file successfully loaded and encoded!
INFO 0 : USB HxCFloppyEmulator :Convert track data...
DEBUG  : USB Track 0 Size: 25288 bytes
DEBUG  : USB Track 1 Size: 25288 bytes
DEBUG  : USB Track 2 Size: 25288 bytes
DEBUG  : USB Track 3 Size: 25288 bytes
DEBUG  : USB Track 4 Size: 25288 bytes
DEBUG  : USB Track 5 Size: 25288 bytes
DEBUG  : USB Track 6 Size: 25288 bytes
DEBUG  : USB Track 7 Size: 25288 bytes
DEBUG  : USB Track 8 Size: 25288 bytes
DEBUG  : USB Track 9 Size: 25288 bytes
DEBUG  : USB Track 10 Size: 25288 bytes
DEBUG  : USB Track 11 Size: 25288 bytes
DEBUG  : USB Track 12 Size: 25288 bytes
DEBUG  : USB Track 13 Size: 25288 bytes
DEBUG  : USB Track 14 Size: 25288 bytes
DEBUG  : USB Track 15 Size: 25288 bytes
DEBUG  : USB Track 16 Size: 25288 bytes
DEBUG  : USB Track 17 Size: 25288 bytes
DEBUG  : USB Track 18 Size: 25288 bytes
DEBUG  : USB Track 19 Size: 25288 bytes
DEBUG  : USB Track 20 Size: 25288 bytes
DEBUG  : USB Track 21 Size: 25288 bytes
DEBUG  : USB Track 22 Size: 25288 bytes
DEBUG  : USB Track 23 Size: 25288 bytes
DEBUG  : USB Track 24 Size: 25288 bytes
DEBUG  : USB Track 25 Size: 25288 bytes
DEBUG  : USB Track 26 Size: 25288 bytes
DEBUG  : USB Track 27 Size: 25288 bytes
DEBUG  : USB Track 28 Size: 25288 bytes
DEBUG  : USB Track 29 Size: 25288 bytes
DEBUG  : USB Track 30 Size: 25288 bytes
DEBUG  : USB Track 31 Size: 25288 bytes
DEBUG  : USB Track 32 Size: 25288 bytes
DEBUG  : USB Track 33 Size: 25288 bytes
DEBUG  : USB Track 34 Size: 25288 bytes
DEBUG  : USB Track 35 Size: 25288 bytes
DEBUG  : USB Track 36 Size: 25288 bytes
DEBUG  : USB Track 37 Size: 25288 bytes
DEBUG  : USB Track 38 Size: 25288 bytes
DEBUG  : USB Track 39 Size: 25288 bytes
INFO 0 : Starting emulation...
INFO 1 : Write HFE file C:\Downloads\MMCPM231_DSK.hfe for the standalone emulator.
INFO 1 : 40 tracks written to the file
But, now when I open the MMCPM231_DSK.hfe file with VFD I just get Drive A: with no files. I set Drive A:
as a RAM Drive.

I've tried four files, and they all act the same:
CPM22132_DSK.hfe
J3SDDD40_DSK.hfe
kaypro2_DMK.hfe
MMCPM231_DSK.hfe

Do you have any ideas?

Thanks.

Larry

Jeff
Site Admin
Posts: 8092
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: How to read 5 1/4" & 3 1/2" Floppies into Software for .

Post by Jeff »

ldkraemer wrote:I finally figured out how to load my *.DSK images that I had previously built with my Catweasel board.
I was thinking that the track Indicator on the bottom of the Window would advance as the file was read,
but that isn't the case.

The *.hfe files were built and I looked at the *.LOG files. Here is the LOG file for MMCPM231.DSK:
But, now when I open the MMCPM231_DSK.hfe file with VFD I just get Drive A: with no files. I set Drive A:
as a RAM Drive.

I've tried four files, and they all act the same:
CPM22132_DSK.hfe
J3SDDD40_DSK.hfe
kaypro2_DMK.hfe
MMCPM231_DSK.hfe

Do you have any ideas?

Thanks.

Larry
VFD ?!? But VFD allow you to load a DOS/FAT floppy image into windows ! Windows will not "understand"/support others file system !

https://hxc2001.com/floppy_drive_emulat ... l#download

If you to check the conversion use this version:
https://hxc2001.com/download/floppy_driv ... 2_beta.zip
And have a look to the track viewer.

ldkraemer
Posts: 51
Joined: Thu Feb 28, 2013 3:47 am

Re: How to read 5 1/4" & 3 1/2" Floppies into Software for .

Post by ldkraemer »

Jeff,
Is there a way to view or access the contents of my CPM22132_DSK.hfe file using Windows XP?

How would I add or remove files from the *.hfe image before using the .hfe on the SLIM hardware?

Thanks.

Larry

Post Reply