Re: [M100] Basic file ending question

Thanks for the info Tom. I modified my test file and added two zero bytes. No change. Interesting that it works fine on my NEC but only on the first bank. I seem to recall that I wasn't able to do this on banks 2 and three before. My T102 has the same issue. It's a mystery for now. I'll keep

Re: [M100] Building VirtualT

On Fri, Mar 27, 2020 at 6:18 PM Brian K. White wrote: > On 3/27/20 9:14 PM, Kevin Becker wrote: > > The official sourceforge version builds on Fedora 31 with the distro > > FLTK cleanly for me now. Thanks! > > > > As a side note, I'm leery of sourceforge too, but it has changed > > ownership

Re: [M100] Building VirtualT

On Fri, Mar 27, 2020 at 6:14 PM Kevin Becker wrote: > The official sourceforge version builds on Fedora 31 with the distro FLTK > cleanly for me now. Thanks! > > As a side note, I'm leery of sourceforge too, but it has changed ownership > again since the days when they were injecting adware and

Re: [M100] Building VirtualT

On 3/27/20 9:14 PM, Kevin Becker wrote: The official sourceforge version builds on Fedora 31 with the distro FLTK cleanly for me now. Thanks! As a side note, I'm leery of sourceforge too, but it has changed ownership again since the days when they were injecting adware and such into

Re: [M100] Basic file ending question

Normally, a BASIC program wont' have control characters encoded in the program itself Normally, but only normally. There are basic files with all kinds of things embedded. They are uncommon and they are hacks to get around other limitations, but they exist and they work with a real M100

Re: [M100] Building VirtualT

The official sourceforge version builds on Fedora 31 with the distro FLTK cleanly for me now. Thanks! As a side note, I'm leery of sourceforge too, but it has changed ownership again since the days when they were injecting adware and such into installers. On Fri, 2020-03-27 at 20:01 -0400,

Re: [M100] Basic file ending question

In memory, a BASIC program should end with three zero bytes. The end of the last line is a null, followed by a 16-bit null pointer. (The first two bytes of a line are a 16-bit pointer to the beginning of the next line.) However, it looks like the files I have saved on my LaddieAlpha root all end

Re: [M100] Basic file ending question

Thanks Ken, That's what I'm seeing here. But both Windows and Linux are giving the same results so I suspect I'm missing something. Time to walk away and clear my brain before I try to tackle it again. At least I have a working TPDD emulator with Directory and Sardine support that should be

Re: [M100] Building VirtualT

I've deleted github.com/bkw777/VirtualT because the upstream original builds cleanly now, and although I don't love sourceforge, it does turn out to offer basic collaboration like github/gitlab, where anyone can make an account, fork, modify, and submit back to the original, all browseable in

Re: [M100] Basic file ending question

But I don't believe the final h bytes are written to the file when saving ... only the final 00h line ending byte. The h is an in-memory only termination, at least looking at the tokenized .BA files I have available. Ken On 3/27/20 4:36 PM, Kurt McCullum wrote: Yes, tokenized BASIC.

Re: [M100] Basic file ending question

On Fri, Mar 27, 2020 at 3:25 PM Kurt McCullum > wrote: I've been working on a Python version of mComm to run on a Linux box I've got setup. Quick question about Basic files. Is there a specific file ending that Basic is looking for? BASIC looks for

Re: [M100] Basic file ending question

Yes, tokenized BASIC. My guess is I'm missing a byte but I'll have to do a hex file comparison from a windows machine vs linux to see what the problem is. Kurt On Fri, Mar 27, 2020, at 4:04 PM, John R. Hogerhuis wrote: > > > On Fri, Mar 27, 2020 at 3:25 PM Kurt McCullum wrote: >> __ >> I've

Re: [M100] Basic file ending question

On Fri, Mar 27, 2020 at 3:25 PM Kurt McCullum wrote: > I've been working on a Python version of mComm to run on a Linux box I've > got setup. Quick question about Basic files. Is there a specific file > ending that Basic is looking for? > > I ask because I can create a hello world program, save

[M100] Basic file ending question

I've been working on a Python version of mComm to run on a Linux box I've got setup. Quick question about Basic files. Is there a specific file ending that Basic is looking for? I ask because I can create a hello world program, save it with TS-DOS, re-load it and everything works. BUT when I

Re: [M100] Uninstall Rex from memory

Ah! Sorry my misunderstanding. When I read power cycling, I thought something along the lines of doing a soft reset would reload the REXmgr. Which would be a neat trick, but not something I'd ever observed mine doing, but that could have been because the firmware wasn't the latest or something.

Re: [M100] Uninstall Rex from memory

Power-cycling on its own will not restore REXMGR, no. However, power-cycling is a necessary step to restoring REXMGR (before running CALL63012) as it forces REX back to "bootstrap" mode where flash block 0 is active, as Stephen says. -Josh On Fri, Mar 27, 2020 at 1:50 PM Stephen Adolph wrote:

Re: [M100] Uninstall Rex from memory

what do you mean by "power cycling never works on mine" what are you expecting to happen? power cycling REX returns it to "nominal",where block 0 is active. On Fri, Mar 27, 2020 at 1:31 PM James Zeun wrote: > > > Power cycling never works on mine, I had a lot of issues getting my REX > working

Re: [M100] Uninstall Rex from memory

Power cycling never works on mine, I had a lot of issues getting my REX working in my M100. Calling it does the trick though, I think I'm using the most recent firmware. Just spend last hour typing away on my M100 - DVI setup, I could get used to this hehe. Though after saving my document to

Re: [M100] Uninstall Rex from memory

Also CNTL-X from MENU works. It is a keyboard shortcut for REX. Assume you are on latest software. What de-install means 1) the hooks REX uses to interfere with the OS are removed End result * any optrom that was configured and made available, remains available, until you power off * this

Re: [M100] Uninstall Rex from memory

Thanks Josh! I just figured it out and feel a prize fool lol I've got the extension cable for my DVI and thought I'd figure out a procedure for using my DVI alongside my REX. Sent from my iPad > On 27 Mar 2020, at 3:18 pm, Josh Malone wrote: > > Enter rexmgr and select DeIn (F7) to

Re: [M100] Uninstall Rex from memory

> On Mar 27, 2020, at 8:15 AM, James Zeun wrote: > I've never done this before, but I know someone mentioned I could use a > command to uninstall the rex manager from memory. It's not as simple as KILL > "rexmgr" is it? Run RexMgr and then hit F7 (DeIn) to de-install.

Re: [M100] Uninstall Rex from memory

Forget I asked this, I just figured it out *hides face* The words "big" and "idiot" come to mind ;-) Sent from my iPad > On 27 Mar 2020, at 3:15 pm, James Zeun wrote: > > Hey guys > > I've never done this before, but I know someone mentioned I could use a > command to uninstall the rex

Re: [M100] Uninstall Rex from memory

Enter rexmgr and select DeIn (F7) to uninstall rexmgr On Fri, Mar 27, 2020 at 11:15 AM James Zeun wrote: > Hey guys > > I've never done this before, but I know someone mentioned I could use a > command to uninstall the rex manager from memory. It's not as simple as > KILL "rexmgr" is it? > > >

[M100] Uninstall Rex from memory

Hey guys I've never done this before, but I know someone mentioned I could use a command to uninstall the rex manager from memory. It's not as simple as KILL "rexmgr" is it? Sent from my iPad