[CSDb] - User Forums - Worst VICE bug in history (RAM error/BASIC)

You are not logged in - nap

CSDb User Forums

Forums > C64 Coding > Worst VICE bug in history (RAM error/BASIC)

2015-11-13 08:01

SIDWAVE
Account closed

Registered: Apr 2002
Posts: 2238

Worst VICE bug in history (RAM error/BASIC)

yeah.. no, its real..

1 hour of work is lost, and i have to do it all over again.
i ran super writer editor (super poker) that has been working ffrom day 1 for 30 years, and i wrote a message it took 1 hour to write.

its all fucked up, and the text is full of zeros, every 2nd letter.

some strange catastophe error with vice happened, and it has run a fully working BASIC program, and poked the data into ram wrong, so the text cant be saved.. it has
a recurring simple bug.:

text typed from basic into ram, as super pokwer does, it has a 0 between every letter. first 3rd of it, then there is some text that is 100% as it shall be (complete with cursor moved, and color changes etc), and the last 40% of the text has the same bug as all in the start, every single key/char that was typed into ram, has a 0 between every letter/chr$ that was typed.

so now, my who work is destroyed, because VICE apparently cant run BASIC programs properly anymore ?

i dont know how this shit is possible, but the error is very systematic.

EVERY byte entered into ram, has a 0 byte between every value...

looks like a simple systematic RAM error in VICE.. that somehow got activated.

i kid you not, im a pro, and i dont want any stupid arguments out of this.

i can fix the text by removing all the zeroes between the typed letters in the message, manually, and perhaps save it all from sure death this way. at least it looks that way.

im almost crying..
i never expected such a freak accident to happen.

what could cause VICE to advance 2 bytes in ram, every time the poke in the basic program only advances 1 byte in ram ?

clearly such an error should be easy to find, but what strange shit in VICE can cause this ?

oh god...
i just feel so sad right now.. this thing i wrote is a part of the 30 year anniversary..

(drained for power now, and sad)

... 20 posts hidden. Click here to view all posts....

2015-11-13 17:31

chatGPZ

Registered: Dec 2001
Posts: 11386

i just hope that at some time in the future you will actually realise that what ian wrote is infact totally correct - the program is broken and cant work with such huge amount of text. and the very same thing will happen on a real c64 of course.

2015-11-13 18:15

Bitbreaker

Registered: Oct 2002
Posts: 508

All the piss answers were just the polite version to let you know that you suck in using a computer. As already mentioned, Ian gave you an elaborate explanation on what went wrong in a technical way. Now go and ragequit anyway, it is about time. You loop back in a week anyway, as usual.

2015-11-13 18:17

SIDWAVE
Account closed

Registered: Apr 2002
Posts: 2238

since the text is 5000-8000 ca, it works.
as i already wrote, the first 30% of text in $5000 is wrong from start, and i didnt know, and it cannot mess up $5000 when i reach about 8000 and message is done.

i hate to repeat myself, but you are not taking this bug report serious at all.

you claim that C64 will mess up something 5000-8000 because i have done something wrong, when it all worked perfect always, and there is ram for text up to $9000 where superwriter program is, and also, i can anytime move the text to $1000..

at no point not a single time have you tried to believe or want to believe that someway a strange poke+increase byte+2 has happened by itself.

end

2015-11-13 18:18

Danzig

Registered: Jun 2002
Posts: 440

I recently found this in the vice sources...

if( get_day_of_week()==DAY_FRIDAY
 && get_day_of_month()==13 
 && !stricmp("sidwave", online_reflector->verify_ip_with_logged_on_csdb_account(ip))) {
  utf16_for_funny_petscii_results = 1;
}

has it smth to do with the problem?

Previous - 1 | 2 | 3 - Next

Refresh

Subscribe to this thread: