EMU is giving me a checksum error???????
2009-05-15 by solacerodgers
Yahoo Groups archive
Index last updated: 2026-04-29 00:09 UTC
Thread
2009-05-15 by solacerodgers
My roms will not read in the simm oard yet every test passes flawless except the rom diag test where i get a OS Checksum = D28DE6CC message. Well i have spent the last few days reading up on systex and bought midiquest as it has a way to check the systex data and send systex messeges and what ever but i cant get anything figured out. I know its a error but i need to know how bad? Anyone got any ideas?
2009-05-15 by woodsworth1
I think that the output of the ROM test is just a checksum value (and if the ROM is unchanged then you can match the checksum against the expected value). I'm not sure that this is an error. Your problem is not clear. What is your XL7 not doing (that you expect it to do)? And when did the functionality change? Also, what do you expect MidiQuest to do? As a guess it seems your sound ROMS (in the SIMM slots) are not available[?] If this is the case you should be aware that the EMU modules are particular in the way in which SIMMs are installed. You must have them in consecutive slots from slot zero up. If you have an empty SIMM slot then SIMMs in larger numbered slots may not be available. [SIMMs may or may not work if you do not adhere to this rule but I've found that 'not working' is more likely] -- --- In xl7@yahoogroups.com, "solacerodgers" <solacerodgers@...> wrote:
> > My roms will not read in the simm oard yet every test passes flawless except the rom diag test where i get a OS Checksum = D28DE6CC message. Well i have spent the last few days reading up on systex and bought midiquest as it has a way to check the systex data and send systex messeges and what ever but i cant get anything figured out. I know its a error but i need to know how bad? Anyone got any ideas? >
2009-05-15 by Ty Rodgers
From: woodsworth1
Subject: [xl7] Re: EMU is giving me a checksum error???????
To: xl7@yahoogroups.com
Date: Friday, May 15, 2009, 7:54 AM
I think that the output of the ROM test is just a checksum value (and if the ROM is unchanged then you can match the checksum against the expected value). I'm not sure that this is an error.
Your problem is not clear. What is your XL7 not doing (that you expect it to do)? And when did the functionality change? Also, what do you expect MidiQuest to do?
As a guess it seems your sound ROMS (in the SIMM slots) are not available[?] If this is the case you should be aware that the EMU modules are particular in the way in which SIMMs are installed. You must have them in consecutive slots from slot zero up. If you have an empty SIMM slot then SIMMs in larger numbered slots may not be available. [SIMMs may or may not work if you do not adhere to this rule but I've found that 'not working' is more likely]
--
--- In xl7@yahoogroups. com, "solacerodgers" wrote:
>
> My roms will not read in the simm oard yet every test passes flawless except the rom diag test where i get a OS Checksum = D28DE6CC message. Well i have spent the last few days reading up on systex and bought midiquest as it has a way to check the systex data and send systex messeges and what ever but i cant get anything figured out. I know its a error but i need to know how bad? Anyone got any ideas?
>
2009-05-15 by woodsworth1
OK. I checked again and the "Program ROM test" does indeed merely output a checksum value. If you do the "Sound ROM test" you should be able to select a slot to test the SIMM in that slot. If you select a slot without a ROM in it you'll get a "No ROM in slot" message. MidiQuest will not help you at all with this problem (your hardware not seeing the ROMs). I have found the EMU modules persnickety in the past. Sometimes they seem to not find the ROMs that I think they should and I need to move the ROMs to get it to work. I have not been in a position where they haven't worked after some juggling, and I've been left wondering whether I imagined it or didn't seat the ROM SIMMs properly. I remember being alarmed more than once that the module hade been domaged during changes that I made to the ROM SIMMs! Anyway, do the simple stuff... #1. check the flashing on the SIMM edge connector and make sure its clean #2. check that the SIMM sockets are clean (free from debris) and they are undamaged. Its not easy to damage them, but it is possible. #3. place the mp-7 ROM in slot 0 - ensure that it is seated correctly - and leave the XL-2 rom out [this should be your original working setup] #4. power up and verify that your original configuration still works. If not you have a problem ;-) If you put two roms in with the same ROM ID [eg Mo'PHATT & MP-7, or sounds of the ZR & HALO (QROM), or just two the same] then the OS will tell you about the error and you'll just get the presets from the lowest numbered slot only - but importantly you get a message and you still get presets. #5. Power off and try again with just the XL-2 rom in slot 0. #6. Now try with both ROMs Let us know how you fare. --- In xl7@yahoogroups.com, Ty Rodgers <solacerodgers@...> wrote:
> > Yeah i have had it for almost 3 years and recently added a xlead v2 rom to the mp7 and after i put it in the roms would not show up in the presets. I have tried moving it to every possible simm slot and resetting but something is odd here. Its the original mp7 rom that came with the unit not a copy or emulation so its got me so confused. would you suggest i just put the rom back in simm slot 0 and then try to get it to reset again? >
2009-05-15 by Ty Rodgers
From: woodsworth1
Subject: [xl7] Re: EMU is giving me a checksum error???????
To: xl7@yahoogroups.com
Date: Friday, May 15, 2009, 9:46 PM
OK. I checked again and the "Program ROM test" does indeed merely output a checksum value. If you do the "Sound ROM test" you should be able to select a slot to test the SIMM in that slot. If you select a slot without a ROM in it you'll get a "No ROM in slot" message.
MidiQuest will not help you at all with this problem (your hardware not seeing the ROMs).
I have found the EMU modules persnickety in the past. Sometimes they seem to not find the ROMs that I think they should and I need to move the ROMs to get it to work. I have not been in a position where they haven't worked after some juggling, and I've been left wondering whether I imagined it or didn't seat the ROM SIMMs properly. I remember being alarmed more than once that the module hade been domaged during changes that I made to the ROM SIMMs!
Anyway, do the simple stuff...
#1. check the flashing on the SIMM edge connector and make sure its clean
#2. check that the SIMM sockets are clean (free from debris) and they are undamaged. Its not easy to damage them, but it is possible.
#3. place the mp-7 ROM in slot 0 - ensure that it is seated correctly - and leave the XL-2 rom out [this should be your original working setup]
#4. power up and verify that your original configuration still works. If not you have a problem ;-)
If you put two roms in with the same ROM ID [eg Mo'PHATT & MP-7, or sounds of the ZR & HALO (QROM), or just two the same] then the OS will tell you about the error and you'll just get the presets from the lowest numbered slot only - but importantly you get a message and you still get presets.
#5. Power off and try again with just the XL-2 rom in slot 0.
#6. Now try with both ROMs
Let us know how you fare.
--- In xl7@yahoogroups. com, Ty Rodgers wrote:
>
> Yeah i have had it for almost 3 years and recently added a xlead v2 rom to the mp7 and after i put it in the roms would not show up in the presets. I have tried moving it to every possible simm slot and resetting but something is odd here. Its the original mp7 rom that came with the unit not a copy or emulation so its got me so confused. would you suggest i just put the rom back in simm slot 0 and then try to get it to reset again?
>