Emax

I thought someone loaded some into the group files section after the last round of discussion about this?

Although this reinforces my argument in support of SCSI.
The whole problem with Floppy was that on EVERY floppy, you have to have the OS.
So, if you change to a new OS version, you must load in the OS and then save it on every floppy.
HxC continues with that method, in that every “disk” image you make has to have that OS in there - the exact SAME OS.
To change it to something else (like the 4.0 OS to use EmuSer, or SE or NOT SE, etc) - same activity again.
So HxC - if you have 99 banks, you have to perform this activity 99 times.

SCSI- you load 1 OS on the HD / image (which holds 35 floppies), and you are done.

For SCSI, you would perform this operation 3 times for 3 HD/images for a total of 105 banks…
When you have an up and running hard disk / device which you booted from, you can take a disk with ANY OS on it, and load that bank in and SAVE that bank onto the HD if desired.
Since it is loading the OS from the Hard Disk, you don’t run into the problem of the version / sw mismatch from the disk.

But that’s just my opinion...


-T

On Feb 8, 2016, at 12:58 PM, Garth Hjelte garth@... [emax] <emax@yahoogroups.com> wrote:

At 12:24 PM 2/8/2016, you wrote:

>Does anyone here have EMAX I SE HxC files they could either share with me or even sell to me?
>I've had this HxC reader installed for months now, and it seems like such a pain to convert these sample banks into HFE files that the HxC drive can use.

When you say "these sample banks", which ones are you speaking of, and why is it a hassle? What is the work you have to do to get them into the HFE format? 

Garth Hjelte
Sampler User






[Non-text portions of this message have been removed]