E-mu Emulator Sampler User Forum for the EIII EII EI and EIII XP - Recent Posts

Welcome, Guest. Please login or register.
Did you miss your activation email?
October 18, 2017, 02:07:24 AM
Home Help Search Login Register
News: Want to register? Then please don't use a Hotmail, Yahoo or Gmail address. They'll block the activation email.
Still having problems activating your account? Send an email to: EIII @ telenet.be

+  E-mu Emulator Sampler User Forum for the EIII EII EI and EIII XP
|-+  Recent Posts
Pages: 1 2 3 4 5 6 7 8 [9] 10

 on: August 25, 2017, 09:45:09 AM 
Started by who - Last post by lunatic
Ok, so I have found the part numbers. I had some gibberish on my display at first too. Actually though changing the hex inverter to the Texas Instruments type you have installed did the trick. The one that was installed in my EII before was also a TI one, this: CD74HCT04E.

Have you checked the conductivity of your solder work?

 on: August 25, 2017, 09:27:42 AM 
Started by Paula - Last post by lunatic
My EII with a dead HD takes about 45 seconds max to boot. I do have the binary image (V 2.3) of the Main ROM which is AFAIK all you need to change. I can not send you the physical EPROM though as I have no possibility to transfer the file to one.

 on: August 24, 2017, 04:03:24 PM 
Started by mg73 - Last post by rectape
Someone help me please to get the chips.

 on: August 24, 2017, 05:08:58 AM 
Started by alka - Last post by obsoletemachines
easy to make.

Lindy do a DIY 9pin apple lead with a 9pin rs422 mini DIN on one end and free leads on the other end.  Buy this and then buy a DB 25 plug and backshell.

If you are serious then use ferrite cores too to lower EMI the Lindy cable is screened.

 on: August 24, 2017, 05:07:11 AM 
Started by edude - Last post by obsoletemachines

I would advise not to try soldering the inverter back - that has nothing to do with this.

you could try swapping the front panel but it will make no difference, the buffering chips for signalling on the eiiix reside on the main board and not the panel.

i suspect you plugged in the analog board the wrong way - that wide ribbon... can confirm if you did this even once? if so then an octal buffer will have shorted and latched up ...that would prevent ram read and write.

you see, there is a lot of buffering going on in the eiiix - buffering of audio, buffering of signals to the LCD.  there is no 'gate' array or chip it all goes to the National CPU...you latch a buffer up and the bus gets congested.

I don't have a schematic but i've been able to work out how this works as its very elegantly laid out.

I recently bought a faulty Eiiix with a scrambled display and fixed it.

 on: August 24, 2017, 04:55:56 AM 
Started by obsoletemachines - Last post by obsoletemachines
Here is a comparison of the green and sky blue oleds, the sky-blue oled is a new iteration of the 4x20 and has only just come to market.  The green appears much 'greener' with the naked eye.

I have installed a Compact Flash slot in place of the 3.5 inch floppy drive.



 on: August 23, 2017, 02:36:44 PM 
Started by luncheonticket - Last post by esynthesist
Great !

I'd like to add that you could have used EMXP to copy the four 250 MB images to each of the SCSI2SD partitons on the SD card. This can be donel by choosing option 1-->5-->3-->1-->select 250MB image-->4 
This option copies a hard disk image to an actual hard disk (here SD card). So if you want to copy the four 250MB images to the four SCSI2SD partitions, you'll have to perform this procedure 4 times (once per image).

After having selected option 4, EMXP will display an overview of the available destination drives.
You then select the SD card drive and press the "C" shortcut key instead of simply pressing ENTER.
Pressing "C" instructs EMXP to scan the SD card for its SCSI2SD partitions and to show each partition as a seperate drive.
To use this feature, you will have to enter the SCSI2SD partition parameters first (=the parameters that were used in scsi2sd-utiil), because EMXP needs this information in order to find/detect the partitions on the SD card. EMXP will ask you to enter these parameters (called a SCSI2SD configuration in EMXP) when you press the "C" shortcut key for the first time.
Once you have entered the SCSI2SD configuration parameters, you won't have to do this again the next time you access the SD card: EMXP will remember the configuration (and up to 10 configurations can be defined for 10 different SCSI2SD setups).

But you can use the truncate & copy approach in Linux as well of course...

 on: August 23, 2017, 10:54:59 AM 
Started by luncheonticket - Last post by luncheonticket
EMXP is great! I just finished creating my custom SCSI2SD card. Cheesy

I ended up creating 4 256mb "disks" for the E-III. Then, I downloaded these Emax banks:


Converted them to EmuIII and saved them in one of the images provided. Then, I joined four 256mb disk files (with a little help from linux Smiley ) and DDed the resulting 1GB file to my SD card. After that, I configured SCSI2SD to use four 256mb LUNs and voila, everything is working as it should!!

Just for future reference, here are the steps I used. I find both linux and osx nicer to work with raw disk images, so I used Debian to combine the disk images, dump them to the sdcard, and configure the scsi2sd interface. I had to use a windows vm for emxp though.

1. In scsi2sd util, I created four devices of exactly 256mb in size. I used SCSI IDs 1, 3, 4 and 5, different serial number for each and automatic sector start. (in this case, these LUNs would start in sectors 0, 524288, 1048576 and 1572864).

2. Then, I saved some banks in the 250mb disk image found here:


3. I padded the 250mb disk file to 256mb using the linux command truncate:

# truncate -s 256M diskfile1.iso

4. Did the same thing to three additional copies of the 250mb disk image:

# truncate -s 256M diskfile2.iso
# truncate -s 256M diskfile3.iso
# truncate -s 256M diskfile4.iso

5. Then, I joined all four disk images in a larger 1GB file:

# cat diskfile1.iso diskfile2.iso diskfile3.iso diskfile4.iso > diskfileS.iso

6. Last, I dumped the 1GB file in the micro sd card:

# dd if=diskfileS.iso of=/dev/mmcblk0 bs=4M
# sync;sync

7. Finally, just popped in the sd card in the scsi2sd interface, and installed it in my EmuIII. It booted successfully, and all the banks I downloaded work great!

Thank you very much for your assistance, this wouldn't be possible without your help. Cheesy

 on: August 22, 2017, 12:11:02 AM 
Started by dvdborn - Last post by dvdborn
This topic has been moved to EIII XP Technical Issues / Tips.


 on: August 14, 2017, 11:01:54 AM 
Started by Paula - Last post by alka
I would also check your PSU molex soldering and harness connections and also check/swap the first of the bottow rows of 4164 DRAM chips.... Here is a comment from Rob on an old Yahoo group post that was helpful to me...

"You can diagnose the failure points as follows:

If the LCD says Boot in Progress the main boot ROM is ok.
If the drive clicks 3 or more times and the EII stalls with Boot in Progress
it is RAM failure or RAM access failure - provided the drive is ok!
If the drive does not click at all and the EII stalls with Boot in Progress
its a main CPU failure.
If the drive clicks 3 times and the LCD is blank and random LED's light its
a Scanner ROM failure.
An Insert Diskette message means the EII cannot see a valid diskette in a
drive - bad media or drive or cable or controller chip
A floppy drive out of alignment or with dirty heads can cause OS loading
failure (Boot in Progeres stall)
A failed floppy drive controller chip will cause OS load failure.
Failed RAM will cause the OS to crash mid session too.

The EII scanning and main CPU's both have local SRAM as well as the main
DRAM. The main DRAM gets used for the OS and samples.

It is important that the PSU has been checked first before starting to
replace components and that you leave the EII to settle for a minute or two
between power on attempts. The Memory Test diskette is really handy for
sorting this type of problem out, but we don't have a copy. The debug ROM we
do have, but you need a RS232 terminal to use it!!

I suggest the following...
1) Check the PSU rails are on spec.
2) Recheck all SRAM, DRAM and ROM is seated.
3) Clean the diskette heads.
4) Check with the list above and see what problems you have still.
5) Check memory by swapping the SRAM chips around and the DRAM chips around.
6) Try a new boot and scanner ROM."

Pages: 1 2 3 4 5 6 7 8 [9] 10

Login with username, password and session length

E-mu Emulator Sampler User Forum for the EIII EII EI and EIII XP - Recent Posts

SEO light theme by © Mustang forums. Powered by SMF 1.1.21 | SMF © 2015, Simple Machines