The new OS rocks. Excellent!
>This is *not* supposed to happen. In fact, this is exactly what the Flash
>Prep step in the update process was designed for - we developed a whole
>piece of code just to avoid this. It worked for me. It worked for Aaron. It
>worked for our Beta testers. Something has unexpectedly gone terribly wrong
>if it erased your data, and we need to figure out exactly how that
happened.
Yes, it erased the last few banks on my machine. Not that it caused any
problems.
Also, the E-loader didn't complete on it's own - it would send the midi
dump, and then display '0% complete' throughout the process - I had to
cancel out of the loader each time. Again, it didn't cause any problems, but
I wanted to make those of you who haven't done the upgrade aware of ths
behaviour, and that the OS updated.
Backing up my patterns was a length process, however. Every so often, I
would get a 'transfer failed' message from the E-loader, and have to
reselect the patterns. From time to time it would also just stop, part of
the way through a pattern. I couldn't do more than one or two patterns at a
time, and often had to repeat the upload several times to get a pattern to
transfer. Does anyone have any ideas why this would occur?
Here is the system I am running:
Win2k, Oct 2001 release
Asus P2B-D motherboard, with latest BIOS, dual PII-400s, 512
megs ram
Unitor mk II midi interface, on serial port.
USB 2.0 PCI card
- MS IE USB mouse
- MS Natural Keys USB keyboard
Rage 128 AGP graphics card
Diamond Stealth Pro PCI graphics card
RME Hammerfall sound card
Also, does anyone know a quick way to blank the entire memory - so I can
remove all the factory patterns?
Jonathan