| |
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) |
|
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
fact: 83 blocks of text, screwed up by vice ram/basic error |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
fact: it worked few weeks ago when i wrote some other message.. i havent updated vice or done anything.. |
| |
Bitbreaker
Registered: Oct 2002
Posts: 508 |
It's a virus!11!
Also: 83 blocks of text /o\ *scared now* |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
clearly a VICE problem! and what faker said /o\ |
| |
Shine
Registered: Jul 2012
Posts: 369 |
Another scener told me some days ago:
"Don't trust an emulator ever!"
Sorry for your lost data ... i would jump out of my window ... (ground floor of course!) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
only a fool blames his tool though. and there are very very very few things that actually dont work correctly in emulators these days. BASIC certainly does :) |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
1. not vice problem
2. save memory, remove every 2nd byte
3. profit |
| |
The Phantom
Registered: Jan 2004
Posts: 360 |
Before I went 100% emulator, there was 1 rule I always lived by when it came to anything on C64. SAVE OFTEN.
In fact, I just finished a part last week. Guess how many work disks I have? 22 for the code, and 5 for the artwork.
SAVE OFTEN.
Sorry for your loss Sidwave ;) |
| |
Tao
Registered: Aug 2002
Posts: 115 |
Step #1: Write the text in vim (or, *shudder*, some other editor) -- bonus: not only do you get to use a good editor, you also get to use a good keyboard
Step #2: Convert the text
Step #3: Copy it to a d64
Step #4: Profit! |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
where is the link to that "super poker" program anyway? if its a bug, it can be reproduced.... right? :)
err... this? Super-Writer ... yeah it will write happily into the I/O registers once you entered enough text, and then crash in funny ways eventually. or perhaps it will overwrite the basic variables before that happens, with similar results.
clearly a VICE bug! |
| |
robozz
Registered: Oct 2003
Posts: 43 |
my thoughts:
1. don't use a 13-line BASIC program on friday the 13th, it's basically asking for trouble!
2. don't blame VICE while using a program which you yourself has written the instructions for.
3. profit :) |
| |
iAN CooG
Registered: May 2002
Posts: 3194 |
Indeed, what groepaz said, after typing just some bytes of text, memory from $9fff backwards is filled with temp strings with all your text interleaved with $00, means that for every char typed, top of mem is filled with 2 bytes too. 83 blocks means 83*256= $5300 bytes, so the text should have ended at $a300 which is clearly BS, this program will eat its own text after ~ $1aa0 bytes, look what happens, "1234567890" is what I typed last :D
>C:6a80 53 53 53 53 53 53 53 53 30 00 00 30 00 39 00 38 SSSSSSSS0..0.9.8
>C:6a90 00 37 00 36 00 35 00 34 00 33 00 32 00 31 00 9d .7.6.5.4.3.2.1..
>C:6aa0 00 9d 00 9d 00 9d 00 9d 00 9d 9d 9d 9d 9d 9d 9d ................
>C:6ab0 9d 31 32 33 34 35 36 37 38 39 30 91 00 11 00 11 .1234567890.....
But don't worry, he's a pro!1 |
| |
TheRyk
Registered: Mar 2009
Posts: 2246 |
I think, he should retype everything on real hw to prove skeptics wrong ;)
For real, MAN, there are so many ways of preventing accidents like that:
a) [Alt+S] for quick snapshot image in WinVICE -> in case of crash you get everything back with [ALT+L]
b) using petcat, here's even a frontend, don't worry, though article is in German, language of tool is English: https://www.c64-wiki.de/index.php/Bas.Edit
c) plain TXT-Editor as already suggested
d) lookee here: https://www.c64-wiki.com/index.php/Memory_%28BASIC%29#String_Va.. there String Heap behaviour is (very roughly) explained
PS:
Quote:1 hour of work ...83 blocks of text
respect :) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
anyone who types out huge amount of text in such terrible editors deserves to be punished for it though :o) |
| |
Bitbreaker
Registered: Oct 2002
Posts: 508 |
In the time of emulators one also uses crosscompiling to get things done. Thus, the avant-garde includes demotext in the .asm sources, that is what i heard as a pro.
!convtab scr
!text "you penis is small! ha! ha!"
|
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
pro dude, since when do you need emulators and cross devving to store text in src ?? I've already did that wirh profi ass... |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
not a single serious answer.
nobody seems to know anything about how it will be possible as i wrote, that it chose today to poke every 2nd adress with the input and not every single byte.
not one single professional IT person answer, just another bull thread on csdb.
as i wrote i can fix it myself, manually, the text is all there, but filled with 0 in between every char in some parts of the text.
clearly i know that i know my computing, and what kinda piss answer just to make a fool out me that this poor answer/bullying/making fun of/claiming i cause basic to skip every 2nd byte..
what you take me for ?
a fool obviously, clearly csdb is never or ever gonna be the place to ask concrete question about weird freak bug..
all you get (from the usual ones and their followers is a complete buyll answer, that i dont know how to use a basic program i used for 30 years and that worked last week.
you dont even wanna try, you just wanna pour shit this way.
so lets forget all about it, i can fix the text, its just a text macro in a pc editor and some convert job..
right lets forget it...
first of all i have virus in my pc
2nd of all i have broken on purpose by mistake because i have zero computer skill, a program i used 30 years, and on top i am blaming vice for this error, because i am an idiot.
ok, write that in your book then.
its all over now, no reason to waste anymore time on this thread full of only piss answer, for the pure sake to make trouble.,
now this long inpolite answer back to you from me, is my answer,.
who cares...
im not doing this again, this is the final time.
if i ever get any strange problem with vice that usually always work, because i have made sure to keep a version that hasnt too many stupid bugs, im not gonna ask anybody in here about help anymore.
i left kindergarten in 1976, and i lets system developer/programmer in 1992..
and you wanna be finished with me ?
haha
c64 scene was built on friendship, letters, diskmags and article, messages in scrollers that people actually read all of it and loved what people wrote in those old days, and .
its all gone to hell, and the sane guys are having the family on facebook..
that this mess you have created because thats how you want it, that it could ever be saved... is an illusion.
no more
my 2 last demos are coming, they are music disks.
all people who liek music, listen.
all people who dont.. doesnt hurt me if you think so...
i can see on some pages on the net where my listeners are, and the 300-400 in the c64 scene are the real sid music lovers.
bah, i quit |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
ian coog, no it will not, and it never did for 30 years.
groepaz, superwriter worked since 1986, nothing has changed.
you can take your little joke that i dont know what im doing, and shove it. eos |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
i just told you all that it worked peerfect as always last week.
and still you write this nonsense answer as you did. ?
its because you want to write nonsense, and not give a shit to fidn out how this bug could happen.
now end.
no words. music need no words. |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
do what you want, you always do what you want anyway. |
| |
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. |
| |
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. |
| |
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 |
| |
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? |
