i dont know anything about operating system codes,or binary or anything. does anyone know anything about the operating system or how to hack it ?

i tryed messing with the OS update file and tryed

i changed COF and RES to OMG and LOL ,

tryed to install it then it gave me this error
http://www.youtube.com/watch?v=N0giEJKFslM

when i restarted my 404 it would not power on, so i put the original 404 os
update on the card and it powered on and reinstalled, so i guess if you dont know what youre doing you can break your 404 and it wont turn on again like i almost did.

yo you would need a gui on your pc and instead of bouncing the info to the card you would need something to connect live stream. i would be interested in givin this a shot on the os.
im a computer programmer so this would be perfect for a little hobby as long as i dont kill my 404....

cool man, what kind of program will capture the stream, im not shure what language the .bin file is in ( binary ? ) i watched some old school programming tutorials so i kind of have an idea what going on with registers stacks and adresses instructions, but not shure how it really works .

do you mean like a 404 emulator as the GUI ?

i bet there is a million features people would love to see built into this, and i would even pay 20 bucks for a hacked OS.

some features i would like to see are . pattern memory, different tempo memory for each pattern, resample sequencer to pad , more card banks ( on,flashing , off. it will give 4 extra banks 48 extra samples) . if i think of anymore ill write them down here.

I think, that if you change anything, the crc doesn't match anymore. So the 404 doesn't start up.

Yes, I would expect a checksum error if you change the binary. That would be a value in the header of the update file that is calculated from some method of summing ALL the o/s data in the update file. It would be nice if the check was done before flashing it into the o/s memory, but it wouldn't be the first Roland device that does it afterwards. It's fortunate it didn't harm the bootstrap code (maybe that's protected and not part of the o/s) or it wouldn't have let you put a good o/s back!

Jim

I think that in order to check if the right version of the os is installed, the checksum is written some place else in (protected) memory. So with each new update, a different checksum is written to that piece of memory and checked on startup.
So if you want to change the os, find the crc first.

yea wow, i feel lucky i didnt break it, i wonder how deep the safety protector goes before it breaks for good. the error is FE7 . when you mess with the update bin.

does anyone know what kind of language the 404 os is ? because i bet you can do little blinky light shows with the pads, or make them look like decibal meters, or probably circuit bend codes for the bend the fx .