Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
String Space Corrupt
#1
What does it mean? I've hardly put that much in this program and it's showing up before the program even seems to execute...
Reply
#2
That error is almost always caused by something overwriting parts of QB's string memory.

Check for the following:
- BLOADing to the wrong segment and/or address
- POKEing to the wrong segment and/or address
- Passing the wrong segment and/or address to any library function that writes over memory, like CopyEmsToMem
- CALL ABSOLUTE call to asm code writing over the wrong memory
Reply
#3
Nope, none of those are the problem, seriously, this is just weird. I'm not doing anything different than what I've done before...
Reply
#4
Posting the code COULD help us out a bit, you know...
am an asshole. Get used to it.
Reply
#5
Well now, that's where everything just sucks, because it's in my secret game. Therefore, I've put myself in this mess and at the same time made it about 5 times as hard to solve (yep, PJ would do something like that)
Reply
#6
It's easy to do this if you mess with strings at all. I mean at all. (asm or varptr, etc.)

You also can get it if you are running low on string space.

-[Unknown]
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)