Eeeek! Help!!

Any problems with your Ultra sampler should be reported here, hopefully someone might know what's wrong.

Moderators: ezman, stu, Ole

Eeeek! Help!!

Postby Spleen » Sat Feb 28, 2004 3:23 pm

my system

self-build DAW PC
MOTU Midi Express Parallel
ST Audio DSP2000 10/10 soundcard
E-MU E6400 Ultra fully loaded w/ int IDE HD (self-fitted)
JV2080
K2000r
Obie 6r
various outboard fx, none midi'd up
only using midi to connect to EMU, no SCSI at all.

Please read the whole thing, the bizzarre EMU stuff is at the bottom!

Something very weird happened in my studio last night. I was making a tune, with a few softsynths, some patches from my JV2080 and no patches loaded on my EMU. a mate came round who I've been doing some tunes with so I closed the tune I was working on, opened his tune. Loaded the patch from the internal HD on the EMU, pressed play and the whole thing monged out badly. I got a BSOD on my PC and the soudcard emitted a loud continual buzzing noise. The stop error on the PC noted MotuMidi.sys at the bottom, so just to be on the safe side, I uninstalled both the midi interface and the soundcard and reinstalled them. The same thing happened. I slept on it. Came to load my tune, which had been fine before all of this happened and it went mental again. Another BSOD and this time a stop error saying DRIVER_CORRUPT_MMPOOL
Anyway, this was too much. I always keep a regular disk image of my system handy for this kind of thing, so I loaded it. Rebooted everything. Now the PC seems to be fine. I haven't loaded my mates tune and I'm not going to. Mine works ok. Now the weird bit. My EMU no longer sees it's internal IDE HDD. Nada. Just the floppy. It worked at 2100 last night coz I loaded patches off it. Now nothing. I fitted it myself months ago and it's worked fine since. Help!!!

any ideas are welcome, I have 20Gb of stuff on there!

thanks
Spleen
 
Posts: 2
Joined: Sat Feb 28, 2004 3:10 pm
Location: UK

Postby ezman » Sat Feb 28, 2004 4:21 pm

Shit mine I don't know what to say! Unless a wire has come loose which doesn't sound likely then the disk may be corrupt - BUT...to be sure....

1. If you dare upgrade your OS to EOS4.7 (if it isn't already) or/and reinitialise your machine - I think you do this by getting into the tests menu (password 1358).

2. Reseat all wires for the drive.

Anybody else got any ideas?
Ezman
ezman
 
Posts: 340
Joined: Mon Apr 14, 2003 8:14 pm
Location: Leeds, UK

Postby Spleen » Sat Feb 28, 2004 6:04 pm

Thx Ezman,

I was running 4.7. I booted from 4.6 and then reinstalled 4.7 to see if it woyuld work..no joy. I think I'm going to cry...
Spleen
 
Posts: 2
Joined: Sat Feb 28, 2004 3:10 pm
Location: UK

Postby sampleandhold » Sun Feb 29, 2004 1:18 am

i had something like this happen with my zip drive. i plugged in my cd rom and lost my zip. what i ended up having to do was unplugge the cord that had gone from the zip to the powerstrip to get the emu to reconize it. seriously, that is the only way i could get it to come up. not unplugging it from the strip, not turning the sampler off. just that. i even recreated the incident and found that what i did before was the only way to get the zip back.

so i am kind of curious to see if you can get the hd back by opening up the kit and unhooking the cord inside from the board, or hd. that is what i would do from the previous experiance. but first, maybe take the power cord from the sampler and disconnect that from the sampler then hook it back up.

other then that i am out. strange, but true, what happened with the zip drive.

hope you get it sorted.
"{jU$t-n3Rv0U$-N-+h3-@Ll3y-W@y}"
sampleandhold
 
Posts: 581
Joined: Tue Apr 15, 2003 4:38 am


Return to EOS:Troubleshooting