Emax

At 09:59 PM 2/8/2016, you wrote:

>Emax doesn’t have enough system memory to hold the complete OS, so it loads in the relevant module (section) of OS from disk when accessed….this is discussed in the guides.

OK, thanks. That's what I thought. The earlier Ensoniq's were like that too.

>So yes- the OS needs to be the same from disk to disk to disk.
>But if you boot from Hard Disk, it KNOWS you booted from Hard Disk, and keeps pulling the OS section from there, not floppy.
>If you stick in a floppy, it only loads or saves the bank information (unless you choose an OS write function from the menu, of course).

OK, thanks. I'll have to start including in our programs a bulk thing that standardizes the OS over many images. Shouldn't be difficult. We are in the last stages of writing and creating Emax I floppy images, mostly for the purpose of floppy emulator use. Chicken Systems programs read any Emax disk or image but doesn't currently write to them.

Lastly, we have a Emax SE here. They didn't come with SCSI (the SE Plus did). I see posts here going back to 2010 about a 3rd-party SCSI. Is it available, do most Emax I people use them, and how useful is it because as I understand the Emax is only 0.5mb as most? (SCSI is fast and fun but if you only have half-a-meg it devalues SCSI quite a bit.)  

Garth Hjelte
Sampler User