+/IM.logon (login mods) about imagebbs HOT 10 CLOSED

Tested on Hyperdrive, Thunderdrive, uIEC/SD2IEC and WinVICE.
Could not duplicate problem.
Looks like you got a bad conversion of the IMG2.0 R2 D1.D81 file when you copied it to your working drive.
I'm looking at the original file that I uploaded and in +/IM.logon, line 4040 reads:
4040 fori=1tobr:print#2,tt$(i)r$a%(i):next:close2:return

You were missing the r$ after tt$(i)
r$ is always defined as chr$(13) but you knew that, right?
Anyways, good catch. I will download the .d81 file from facebook and compare it to the one I uploaded.

from imagebbs.

Nothing wrong in that file line 4040 in the one I just now download from facebook.

from imagebbs.

OK, I had to come back to this one as well after re-reading the issue and thinking about it for awhile.
I know that in 1.2 we were always defining r$=chr$(13) all over the place but in 2.0 it's not supposed to be that way.
During bootup, line 3064 in the im file sets r$=chr$(13) as a reserved variable. It should never be changed. So, there should be no reason to have to define r$ in every module that is run, in fact, none of the +/IM. modules define r$ and even the mother program, +.IM, doesn't define r$ so probably, somewhere among all the files included in Image 2.0, there might be somewhere that someone (even myself) might have defined r$ as a different value than chr$(13). It would have been in something that was run prior to entering the IM section and could explain why you saw the problem and I didn't.

Wow! Finding that might take awhile. Do you remember what you ran prior to going into the IM section?

from imagebbs.

A little bit of everything, but I think that might be my fault. While I was porting over my responsive prompt feature, I had written a line (it's gone now) that changed a handful of variables over to singles, thinking that none of the singles were system reserved.
r$ was one of those variables.
I didn't have an updated variable or jumpcode cheat sheet, so I had wrote that file to display a$ thru z$ at every possible prompt that shares the (gosub1006) prompt.
After I made my discovery and took notes, I removed the line that redefined variables, so I should be back to stock now. But while I was testing those modules, that line was active.

from imagebbs.

Yeah.... That would explain things. I just spent the past couple of hours checking files included in the 2.0 R2 revision using the Lt.K find /r$=/ command. None of the 2.0 programs had it in there except for when it was defined in im line 3064. I did find several 1.2 conversion +.files that had hits but they all defined r$ as chr$(13)
I think this issue can be closed.

from imagebbs.

Agreed. For future reference would it be better to have chr$(13) or F6? (the reverse K)
I figured out what I had done after I tried to use the editor (WF) and none of the dot commands would work. That's stored in a$ and s$.

Could really use a cheat sheet. (hint)

from imagebbs.

I think the standard has been when you're writing data to a disk file, use r$ between records (a final carriage return should be output when writing to a REL file, but I'm not 100% certain of this). & output statements can use {f6}.

Could really use a cheat sheet. (hint)

A cheat sheet to what?

Have you guys seen the 1.2 cheat sheet I started? I uploaded it to Facebook a while back. Never saw any feedback about it.

from imagebbs.

Yes, I saw it. But it's not entirely accurate for 2.0.
Many of the consistent variables are the same, but there are things like mp%, mt%, and tu$ that were not referenced.
I do use it regularly when I'm working on 1.2 items especially jump tables and lightbar calls, but I'm awful about remembering feedback.

from imagebbs.

This issue should be closed. I think only the originator of the issue can close it. (Jay)

from imagebbs.

Yep, been out of town lately. Closed.

from imagebbs.