Yahoo Groups archive

Emax

Index last updated: 2026-04-28 23:23 UTC

Message

Re: [emax] Re: Baldwin IKE CF addition mayhem

2012-02-22 by jammie

thanks so format it in windows as fat 16

then create a emax hardrive image of 20mb  ez1 blank image

then write os to it

then write that image to the cfcard which foirmats it to the emax system over writing the fat 16 format

thanks

  ----- Original Message ----- 
  From: esynthesist 
  To: emax@yahoogroups.com 
  Sent: Wednesday, February 22, 2012 8:25 PM
  Subject: [emax] Re: Baldwin IKE CF addition mayhem


    
  Since you seems to have managed to write your CF card (on the Baldwin itself I assume), the following is probably not important anymore for you.

  But anyway: errorcode 104 is returned when you try to write an individual Emax bank to a disk which is not *logically* formatted for Emax yet.

  That's why you have to generate an .EZ1 image first and copy (restore) it to the DOS formatted CF card (as I wrote in my initial reply).
  This .EZ1 image contains the file system of the Emax. By copying it to the DOS formatted CF card, the DOS FAT file system is overwritten by the Emax file system. Without this Emax file system, EMXP nor the Emax can save sound banks to the CF card.

  When you format the CF card in the Emax or Emax-II itself, the card is both physically and logically formatted. In that case the card is immediately ready for saving banks to it.

  FYI: Section 6.1 in the EMXP manual explains how to create Emax compatible CF cards with EMXP.

  ///E-Synthesist

  --- In emax@yahoogroups.com, "soundsubs" <soundsubs@...> wrote:
  >
  > > Perhaps I should add something to my previous reply.
  > > When accessing removable disks, EMXP almost always requests an EXCLUSIVE READ and WRITE access. 
  > >>>Thanks again E. this is an important point and has caught me a few times. mostly, windows pops up a window that asks what i'd like to do with the newly inserted drive. often times i miss this. closing it allows EMXP to again read/write to it. 
  > 
  > i was able to get it to TRY to write a file to my drive J. 
  > now its reporting back "Errorcode 104: content of disk in drive J is not compatible with Emax/EMUIII. subcode 7"
  >



  

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

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.