Re: [M100] Starship Management Software

[D10D3 Data]

It's a utility I wrote for use with a Pen and Paper sci-fi RPG I run for
some friends.

On Mon, May 4, 2020, 1:17 PM James Zeun  wrote:

> I think I must have missed this thread somehow, a starship manager? Is
> this a game or some sort of utility to let me keep track of how many red
> shirts I have left :-P
>
> On Mon, 4 May 2020 at 04:18, D10D3 Data  wrote:
>
>> Can you attach or link to your amended M100 version?
>>
>> On Sat, May 2, 2020 at 3:01 AM Jim Anderson  wrote:
>>
>>> > -Original Message-
>>> > I wrote a utility on my NEC 8201A to aid the players in a scifi RPG I
>>> > run. If anyone is curious I've posted the code
>>> > here:  https://pastebin.com/9EJ7JbDN
>>> > It's NEC basic, so it won't run on an M100 without a bit of porting,
>>> but
>>> > if you have a NEC or run Virtual-T in NEC mode you can try it out. It's
>>> > janky and far from optimized but it works.
>>>
>>> Catching up on old posts still.  Hey, that's pretty cool!  I've pasted
>>> in a diff (below my signature) for the mods I made to make it run in M100
>>> mode in VirtualT (including a couple of edits, and fixing a logic error
>>> where editing any cargo item's quantity changes your fuel quantity).  One
>>> thing: it doesn't seem happy unless CARGO.DO is present and populated with
>>> at least dummy data, and it wasn't obvious until I read the code that the
>>> first item in the cargo needs to be fuel.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> jim
>>>
>>>
>>> $ diff SHPSYS.NEC.txt SHPSYS.txt
>>> 2c2,3
>>> < 20  SCREEN 0,0:CLS:LOCATE 10,3:PRINT"INITIALIZING";
>>> ---
>>> > 15  REM ADAPTED TO THE M100 -JRA
>>> > 20  SCREEN 0,0:CLS:PRINT@130,"INITIALIZING";
>>> 44,47c45,48
>>> < 700 LOCATE 0,0:PRINT"SYSTEMS ONLINE"
>>> < 710 LOCATE 0,4:PRINT"N: NAVIGATION";
>>> < 720 LOCATE 0,5:PRINT"C: CARGO MANAGER";
>>> < 730 LOCATE 0,6:PRINT"Q: QUIT";
>>> ---
>>> > 700 PRINT@0,"SYSTEMS ONLINE"
>>> > 710 PRINT@200,"N: NAVIGATION";
>>> > 720 PRINT@240,"C: CARGO MANAGER";
>>> > 730 PRINT@280,"Q: QUIT";
>>> 82,83c83
>>> < 1370 LOCATE 0,0
>>> < 1380 PRINT"1.Abbadon7.Chelsea13.Lungold"
>>> ---
>>> > 1380 PRINT@0,"1.Abbadon7.Chelsea13.Lungold"
>>> 91,92c91
>>> < 1460 LOCATE 0,0
>>> < 1470 PRINT"14.Medusa 20.Shiva"
>>> ---
>>> > 1470 PRINT@0,"14.Medusa 20.Shiva"
>>> 117c116
>>> < 1720 LOCATE 20,0:PRINT"DISTANCE:";
>>> ---
>>> > 1720 PRINT@20,"DISTANCE:";
>>> 119c118
>>> < 1740 LOCATE 20,1:PRINT"DAYS:";:PRINT USING A$; DIST;
>>> ---
>>> > 1740 PRINT@60,"DAYS:";:PRINT USING A$; DIST;
>>> 121,122c120,121
>>> < 1760 LOCATE 20,2:PRINT"FUEL USED:";:PRINT USING A$; DIST*2;
>>> < 1762 LOCATE 20,4:PRINT"Execute Flight";:LOCATE
>>> 20,5:INPUT"Plan?(Y/N)";B$
>>> ---
>>> > 1760 PRINT@100,"FUEL USED:";:PRINT USING A$; DIST*2;
>>> > 1762 PRINT@180,"Execute Flight";:PRINT@220,"";:INPUT"Plan?(Y/N)";B$
>>> 124c123
>>> < 1770 LOCATE 20,5:INPUT"ANOTHER(Y/N)  ";B$
>>> ---
>>> > 1770 PRINT@220,"";:INPUT"ANOTHER(Y/N)  ";B$
>>> 153c152
>>> < 2210 LOCATE 0,0:PRINT"NAME  TON   COST"
>>> ---
>>> > 2210 PRINT@0,"NAME  TON   COST"
>>> 155,157c154,156
>>> < 2230 LOCATE 1,L:PRINT CN$(I);:
>>> < 2240 LOCATE 30,L:PRINT CT%(I);
>>> < 2250 LOCATE 35,L:PRINT CC%(I);
>>> ---
>>> > 2230 PRINT@1+(L*40),CN$(I);:
>>> > 2240 PRINT@30+(L*40),CT%(I);
>>> > 2250 PRINT@35+(L*40),CC%(I);
>>> 160c159
>>> < 2280 LOCATE 0,7:PRINT"SELECT:U/D PAGE:L/R EDIT:ENT QUIT:ESC";
>>> ---
>>> > 2280 PRINT@280,"SELECT:U/D PAGE:L/R EDIT:ENT QUIT:ESC";
>>> 173c172
>>> < 2410 GOSUB 2480:INPUT"TONS:";A$:CT%(SE)=VAL(A$):FUEL%=VAL(A$)
>>> ---
>>> > 2410 GOSUB 2480:INPUT"TONS:";A$:CT%(SE)=VAL(A$):IF SE=1 THEN
>>> FUEL%=VAL(A$)
>>> 175c174
>>> < 2430 IF SE>30 THEN SE=30!SLE IF SE<1 THE SE=1
>>> ---
>>> > 2430 IF SE>30 THEN SE=30 ELSE IF SE<1 THEN SE=1
>>> 180,181c179,180
>>> < 2480 LOCATE 0,7:PRINT" ";
>>> < 2490 LOCATE 0,7:RETURN
>>> ---
>>> > 2480 PRINT@280," ";
>>> > 2490 PRINT@280,"";:RETURN
>>> 183c182
>>> < 2510 IF DIST*2 > FUEL% THEN LOCATE 20,4:PRINT"INSUFFICIENT
>>> FUEL";:LOCATE 20,5:INPUT"";B$
>>> ---
>>> > 2510 IF DIST*2 > FUEL% THEN PRINT@180,"INSUFFICIENT 
>>> > FUEL";:PRINT@220,"";:INPUT">> A KEY>";B$
>>>
>>>
>
> --
> My retro tech blog and general ramblings
> http://bytemyvdu.wordpress.com/
>

Re: [M100] Starship Management Software

[James Zeun]

I think I must have missed this thread somehow, a starship manager? Is this
a game or some sort of utility to let me keep track of how many red shirts
I have left :-P

On Mon, 4 May 2020 at 04:18, D10D3 Data  wrote:

> Can you attach or link to your amended M100 version?
>
> On Sat, May 2, 2020 at 3:01 AM Jim Anderson  wrote:
>
>> > -Original Message-
>> > I wrote a utility on my NEC 8201A to aid the players in a scifi RPG I
>> > run. If anyone is curious I've posted the code
>> > here:  https://pastebin.com/9EJ7JbDN
>> > It's NEC basic, so it won't run on an M100 without a bit of porting, but
>> > if you have a NEC or run Virtual-T in NEC mode you can try it out. It's
>> > janky and far from optimized but it works.
>>
>> Catching up on old posts still.  Hey, that's pretty cool!  I've pasted in
>> a diff (below my signature) for the mods I made to make it run in M100 mode
>> in VirtualT (including a couple of edits, and fixing a logic error where
>> editing any cargo item's quantity changes your fuel quantity).  One thing:
>> it doesn't seem happy unless CARGO.DO is present and populated with at
>> least dummy data, and it wasn't obvious until I read the code that the
>> first item in the cargo needs to be fuel.
>>
>>
>>
>>
>>
>>
>>
>> jim
>>
>>
>> $ diff SHPSYS.NEC.txt SHPSYS.txt
>> 2c2,3
>> < 20  SCREEN 0,0:CLS:LOCATE 10,3:PRINT"INITIALIZING";
>> ---
>> > 15  REM ADAPTED TO THE M100 -JRA
>> > 20  SCREEN 0,0:CLS:PRINT@130,"INITIALIZING";
>> 44,47c45,48
>> < 700 LOCATE 0,0:PRINT"SYSTEMS ONLINE"
>> < 710 LOCATE 0,4:PRINT"N: NAVIGATION";
>> < 720 LOCATE 0,5:PRINT"C: CARGO MANAGER";
>> < 730 LOCATE 0,6:PRINT"Q: QUIT";
>> ---
>> > 700 PRINT@0,"SYSTEMS ONLINE"
>> > 710 PRINT@200,"N: NAVIGATION";
>> > 720 PRINT@240,"C: CARGO MANAGER";
>> > 730 PRINT@280,"Q: QUIT";
>> 82,83c83
>> < 1370 LOCATE 0,0
>> < 1380 PRINT"1.Abbadon7.Chelsea13.Lungold"
>> ---
>> > 1380 PRINT@0,"1.Abbadon7.Chelsea13.Lungold"
>> 91,92c91
>> < 1460 LOCATE 0,0
>> < 1470 PRINT"14.Medusa 20.Shiva"
>> ---
>> > 1470 PRINT@0,"14.Medusa 20.Shiva"
>> 117c116
>> < 1720 LOCATE 20,0:PRINT"DISTANCE:";
>> ---
>> > 1720 PRINT@20,"DISTANCE:";
>> 119c118
>> < 1740 LOCATE 20,1:PRINT"DAYS:";:PRINT USING A$; DIST;
>> ---
>> > 1740 PRINT@60,"DAYS:";:PRINT USING A$; DIST;
>> 121,122c120,121
>> < 1760 LOCATE 20,2:PRINT"FUEL USED:";:PRINT USING A$; DIST*2;
>> < 1762 LOCATE 20,4:PRINT"Execute Flight";:LOCATE 20,5:INPUT"Plan?(Y/N)";B$
>> ---
>> > 1760 PRINT@100,"FUEL USED:";:PRINT USING A$; DIST*2;
>> > 1762 PRINT@180,"Execute Flight";:PRINT@220,"";:INPUT"Plan?(Y/N)";B$
>> 124c123
>> < 1770 LOCATE 20,5:INPUT"ANOTHER(Y/N)  ";B$
>> ---
>> > 1770 PRINT@220,"";:INPUT"ANOTHER(Y/N)  ";B$
>> 153c152
>> < 2210 LOCATE 0,0:PRINT"NAME  TON   COST"
>> ---
>> > 2210 PRINT@0,"NAME  TON   COST"
>> 155,157c154,156
>> < 2230 LOCATE 1,L:PRINT CN$(I);:
>> < 2240 LOCATE 30,L:PRINT CT%(I);
>> < 2250 LOCATE 35,L:PRINT CC%(I);
>> ---
>> > 2230 PRINT@1+(L*40),CN$(I);:
>> > 2240 PRINT@30+(L*40),CT%(I);
>> > 2250 PRINT@35+(L*40),CC%(I);
>> 160c159
>> < 2280 LOCATE 0,7:PRINT"SELECT:U/D PAGE:L/R EDIT:ENT QUIT:ESC";
>> ---
>> > 2280 PRINT@280,"SELECT:U/D PAGE:L/R EDIT:ENT QUIT:ESC";
>> 173c172
>> < 2410 GOSUB 2480:INPUT"TONS:";A$:CT%(SE)=VAL(A$):FUEL%=VAL(A$)
>> ---
>> > 2410 GOSUB 2480:INPUT"TONS:";A$:CT%(SE)=VAL(A$):IF SE=1 THEN
>> FUEL%=VAL(A$)
>> 175c174
>> < 2430 IF SE>30 THEN SE=30!SLE IF SE<1 THE SE=1
>> ---
>> > 2430 IF SE>30 THEN SE=30 ELSE IF SE<1 THEN SE=1
>> 180,181c179,180
>> < 2480 LOCATE 0,7:PRINT" ";
>> < 2490 LOCATE 0,7:RETURN
>> ---
>> > 2480 PRINT@280," ";
>> > 2490 PRINT@280,"";:RETURN
>> 183c182
>> < 2510 IF DIST*2 > FUEL% THEN LOCATE 20,4:PRINT"INSUFFICIENT
>> FUEL";:LOCATE 20,5:INPUT"";B$
>> ---
>> > 2510 IF DIST*2 > FUEL% THEN PRINT@180,"INSUFFICIENT 
>> > FUEL";:PRINT@220,"";:INPUT"> A KEY>";B$
>>
>>

-- 
My retro tech blog and general ramblings
http://bytemyvdu.wordpress.com/

Re: [M100] Starship Management Software

[D10D3 Data]

Can you attach or link to your amended M100 version?

On Sat, May 2, 2020 at 3:01 AM Jim Anderson  wrote:

> > -Original Message-
> > I wrote a utility on my NEC 8201A to aid the players in a scifi RPG I
> > run. If anyone is curious I've posted the code
> > here:  https://pastebin.com/9EJ7JbDN
> > It's NEC basic, so it won't run on an M100 without a bit of porting, but
> > if you have a NEC or run Virtual-T in NEC mode you can try it out. It's
> > janky and far from optimized but it works.
>
> Catching up on old posts still.  Hey, that's pretty cool!  I've pasted in
> a diff (below my signature) for the mods I made to make it run in M100 mode
> in VirtualT (including a couple of edits, and fixing a logic error where
> editing any cargo item's quantity changes your fuel quantity).  One thing:
> it doesn't seem happy unless CARGO.DO is present and populated with at
> least dummy data, and it wasn't obvious until I read the code that the
> first item in the cargo needs to be fuel.
>
>
>
>
>
>
>
> jim
>
>
> $ diff SHPSYS.NEC.txt SHPSYS.txt
> 2c2,3
> < 20  SCREEN 0,0:CLS:LOCATE 10,3:PRINT"INITIALIZING";
> ---
> > 15  REM ADAPTED TO THE M100 -JRA
> > 20  SCREEN 0,0:CLS:PRINT@130,"INITIALIZING";
> 44,47c45,48
> < 700 LOCATE 0,0:PRINT"SYSTEMS ONLINE"
> < 710 LOCATE 0,4:PRINT"N: NAVIGATION";
> < 720 LOCATE 0,5:PRINT"C: CARGO MANAGER";
> < 730 LOCATE 0,6:PRINT"Q: QUIT";
> ---
> > 700 PRINT@0,"SYSTEMS ONLINE"
> > 710 PRINT@200,"N: NAVIGATION";
> > 720 PRINT@240,"C: CARGO MANAGER";
> > 730 PRINT@280,"Q: QUIT";
> 82,83c83
> < 1370 LOCATE 0,0
> < 1380 PRINT"1.Abbadon7.Chelsea13.Lungold"
> ---
> > 1380 PRINT@0,"1.Abbadon7.Chelsea13.Lungold"
> 91,92c91
> < 1460 LOCATE 0,0
> < 1470 PRINT"14.Medusa 20.Shiva"
> ---
> > 1470 PRINT@0,"14.Medusa 20.Shiva"
> 117c116
> < 1720 LOCATE 20,0:PRINT"DISTANCE:";
> ---
> > 1720 PRINT@20,"DISTANCE:";
> 119c118
> < 1740 LOCATE 20,1:PRINT"DAYS:";:PRINT USING A$; DIST;
> ---
> > 1740 PRINT@60,"DAYS:";:PRINT USING A$; DIST;
> 121,122c120,121
> < 1760 LOCATE 20,2:PRINT"FUEL USED:";:PRINT USING A$; DIST*2;
> < 1762 LOCATE 20,4:PRINT"Execute Flight";:LOCATE 20,5:INPUT"Plan?(Y/N)";B$
> ---
> > 1760 PRINT@100,"FUEL USED:";:PRINT USING A$; DIST*2;
> > 1762 PRINT@180,"Execute Flight";:PRINT@220,"";:INPUT"Plan?(Y/N)";B$
> 124c123
> < 1770 LOCATE 20,5:INPUT"ANOTHER(Y/N)  ";B$
> ---
> > 1770 PRINT@220,"";:INPUT"ANOTHER(Y/N)  ";B$
> 153c152
> < 2210 LOCATE 0,0:PRINT"NAME  TON   COST"
> ---
> > 2210 PRINT@0,"NAME  TON   COST"
> 155,157c154,156
> < 2230 LOCATE 1,L:PRINT CN$(I);:
> < 2240 LOCATE 30,L:PRINT CT%(I);
> < 2250 LOCATE 35,L:PRINT CC%(I);
> ---
> > 2230 PRINT@1+(L*40),CN$(I);:
> > 2240 PRINT@30+(L*40),CT%(I);
> > 2250 PRINT@35+(L*40),CC%(I);
> 160c159
> < 2280 LOCATE 0,7:PRINT"SELECT:U/D PAGE:L/R EDIT:ENT QUIT:ESC";
> ---
> > 2280 PRINT@280,"SELECT:U/D PAGE:L/R EDIT:ENT QUIT:ESC";
> 173c172
> < 2410 GOSUB 2480:INPUT"TONS:";A$:CT%(SE)=VAL(A$):FUEL%=VAL(A$)
> ---
> > 2410 GOSUB 2480:INPUT"TONS:";A$:CT%(SE)=VAL(A$):IF SE=1 THEN
> FUEL%=VAL(A$)
> 175c174
> < 2430 IF SE>30 THEN SE=30!SLE IF SE<1 THE SE=1
> ---
> > 2430 IF SE>30 THEN SE=30 ELSE IF SE<1 THEN SE=1
> 180,181c179,180
> < 2480 LOCATE 0,7:PRINT" ";
> < 2490 LOCATE 0,7:RETURN
> ---
> > 2480 PRINT@280," ";
> > 2490 PRINT@280,"";:RETURN
> 183c182
> < 2510 IF DIST*2 > FUEL% THEN LOCATE 20,4:PRINT"INSUFFICIENT FUEL";:LOCATE
> 20,5:INPUT"";B$
> ---
> > 2510 IF DIST*2 > FUEL% THEN PRINT@180,"INSUFFICIENT 
> > FUEL";:PRINT@220,"";:INPUT" A KEY>";B$
>
>

Re: [M100] Starship Management Software

[D10D3 Data]

Nice! Thanks for porting it!

On Sat, May 2, 2020 at 3:01 AM Jim Anderson  wrote:

> > -Original Message-
> > I wrote a utility on my NEC 8201A to aid the players in a scifi RPG I
> > run. If anyone is curious I've posted the code
> > here:  https://pastebin.com/9EJ7JbDN
> > It's NEC basic, so it won't run on an M100 without a bit of porting, but
> > if you have a NEC or run Virtual-T in NEC mode you can try it out. It's
> > janky and far from optimized but it works.
>
> Catching up on old posts still.  Hey, that's pretty cool!  I've pasted in
> a diff (below my signature) for the mods I made to make it run in M100 mode
> in VirtualT (including a couple of edits, and fixing a logic error where
> editing any cargo item's quantity changes your fuel quantity).  One thing:
> it doesn't seem happy unless CARGO.DO is present and populated with at
> least dummy data, and it wasn't obvious until I read the code that the
> first item in the cargo needs to be fuel.
>
>
>
>
>
>
>
> jim
>
>
> $ diff SHPSYS.NEC.txt SHPSYS.txt
> 2c2,3
> < 20  SCREEN 0,0:CLS:LOCATE 10,3:PRINT"INITIALIZING";
> ---
> > 15  REM ADAPTED TO THE M100 -JRA
> > 20  SCREEN 0,0:CLS:PRINT@130,"INITIALIZING";
> 44,47c45,48
> < 700 LOCATE 0,0:PRINT"SYSTEMS ONLINE"
> < 710 LOCATE 0,4:PRINT"N: NAVIGATION";
> < 720 LOCATE 0,5:PRINT"C: CARGO MANAGER";
> < 730 LOCATE 0,6:PRINT"Q: QUIT";
> ---
> > 700 PRINT@0,"SYSTEMS ONLINE"
> > 710 PRINT@200,"N: NAVIGATION";
> > 720 PRINT@240,"C: CARGO MANAGER";
> > 730 PRINT@280,"Q: QUIT";
> 82,83c83
> < 1370 LOCATE 0,0
> < 1380 PRINT"1.Abbadon7.Chelsea13.Lungold"
> ---
> > 1380 PRINT@0,"1.Abbadon7.Chelsea13.Lungold"
> 91,92c91
> < 1460 LOCATE 0,0
> < 1470 PRINT"14.Medusa 20.Shiva"
> ---
> > 1470 PRINT@0,"14.Medusa 20.Shiva"
> 117c116
> < 1720 LOCATE 20,0:PRINT"DISTANCE:";
> ---
> > 1720 PRINT@20,"DISTANCE:";
> 119c118
> < 1740 LOCATE 20,1:PRINT"DAYS:";:PRINT USING A$; DIST;
> ---
> > 1740 PRINT@60,"DAYS:";:PRINT USING A$; DIST;
> 121,122c120,121
> < 1760 LOCATE 20,2:PRINT"FUEL USED:";:PRINT USING A$; DIST*2;
> < 1762 LOCATE 20,4:PRINT"Execute Flight";:LOCATE 20,5:INPUT"Plan?(Y/N)";B$
> ---
> > 1760 PRINT@100,"FUEL USED:";:PRINT USING A$; DIST*2;
> > 1762 PRINT@180,"Execute Flight";:PRINT@220,"";:INPUT"Plan?(Y/N)";B$
> 124c123
> < 1770 LOCATE 20,5:INPUT"ANOTHER(Y/N)  ";B$
> ---
> > 1770 PRINT@220,"";:INPUT"ANOTHER(Y/N)  ";B$
> 153c152
> < 2210 LOCATE 0,0:PRINT"NAME  TON   COST"
> ---
> > 2210 PRINT@0,"NAME  TON   COST"
> 155,157c154,156
> < 2230 LOCATE 1,L:PRINT CN$(I);:
> < 2240 LOCATE 30,L:PRINT CT%(I);
> < 2250 LOCATE 35,L:PRINT CC%(I);
> ---
> > 2230 PRINT@1+(L*40),CN$(I);:
> > 2240 PRINT@30+(L*40),CT%(I);
> > 2250 PRINT@35+(L*40),CC%(I);
> 160c159
> < 2280 LOCATE 0,7:PRINT"SELECT:U/D PAGE:L/R EDIT:ENT QUIT:ESC";
> ---
> > 2280 PRINT@280,"SELECT:U/D PAGE:L/R EDIT:ENT QUIT:ESC";
> 173c172
> < 2410 GOSUB 2480:INPUT"TONS:";A$:CT%(SE)=VAL(A$):FUEL%=VAL(A$)
> ---
> > 2410 GOSUB 2480:INPUT"TONS:";A$:CT%(SE)=VAL(A$):IF SE=1 THEN
> FUEL%=VAL(A$)
> 175c174
> < 2430 IF SE>30 THEN SE=30!SLE IF SE<1 THE SE=1
> ---
> > 2430 IF SE>30 THEN SE=30 ELSE IF SE<1 THEN SE=1
> 180,181c179,180
> < 2480 LOCATE 0,7:PRINT" ";
> < 2490 LOCATE 0,7:RETURN
> ---
> > 2480 PRINT@280," ";
> > 2490 PRINT@280,"";:RETURN
> 183c182
> < 2510 IF DIST*2 > FUEL% THEN LOCATE 20,4:PRINT"INSUFFICIENT FUEL";:LOCATE
> 20,5:INPUT"";B$
> ---
> > 2510 IF DIST*2 > FUEL% THEN PRINT@180,"INSUFFICIENT 
> > FUEL";:PRINT@220,"";:INPUT" A KEY>";B$
>
>

Re: [M100] Starship Management Software

[Jim Anderson]

> -Original Message-
> I wrote a utility on my NEC 8201A to aid the players in a scifi RPG I
> run. If anyone is curious I've posted the code
> here:  https://pastebin.com/9EJ7JbDN
> It's NEC basic, so it won't run on an M100 without a bit of porting, but
> if you have a NEC or run Virtual-T in NEC mode you can try it out. It's
> janky and far from optimized but it works.

Catching up on old posts still.  Hey, that's pretty cool!  I've pasted in a 
diff (below my signature) for the mods I made to make it run in M100 mode in 
VirtualT (including a couple of edits, and fixing a logic error where editing 
any cargo item's quantity changes your fuel quantity).  One thing: it doesn't 
seem happy unless CARGO.DO is present and populated with at least dummy data, 
and it wasn't obvious until I read the code that the first item in the cargo 
needs to be fuel.







jim


$ diff SHPSYS.NEC.txt SHPSYS.txt
2c2,3
< 20  SCREEN 0,0:CLS:LOCATE 10,3:PRINT"INITIALIZING";
---
> 15  REM ADAPTED TO THE M100 -JRA
> 20  SCREEN 0,0:CLS:PRINT@130,"INITIALIZING";
44,47c45,48
< 700 LOCATE 0,0:PRINT"SYSTEMS ONLINE"
< 710 LOCATE 0,4:PRINT"N: NAVIGATION";
< 720 LOCATE 0,5:PRINT"C: CARGO MANAGER";
< 730 LOCATE 0,6:PRINT"Q: QUIT";
---
> 700 PRINT@0,"SYSTEMS ONLINE"
> 710 PRINT@200,"N: NAVIGATION";
> 720 PRINT@240,"C: CARGO MANAGER";
> 730 PRINT@280,"Q: QUIT";
82,83c83
< 1370 LOCATE 0,0
< 1380 PRINT"1.Abbadon7.Chelsea13.Lungold"
---
> 1380 PRINT@0,"1.Abbadon7.Chelsea13.Lungold"
91,92c91
< 1460 LOCATE 0,0
< 1470 PRINT"14.Medusa 20.Shiva"
---
> 1470 PRINT@0,"14.Medusa 20.Shiva"
117c116
< 1720 LOCATE 20,0:PRINT"DISTANCE:";
---
> 1720 PRINT@20,"DISTANCE:";
119c118
< 1740 LOCATE 20,1:PRINT"DAYS:";:PRINT USING A$; DIST;
---
> 1740 PRINT@60,"DAYS:";:PRINT USING A$; DIST;
121,122c120,121
< 1760 LOCATE 20,2:PRINT"FUEL USED:";:PRINT USING A$; DIST*2;
< 1762 LOCATE 20,4:PRINT"Execute Flight";:LOCATE 20,5:INPUT"Plan?(Y/N)";B$
---
> 1760 PRINT@100,"FUEL USED:";:PRINT USING A$; DIST*2;
> 1762 PRINT@180,"Execute Flight";:PRINT@220,"";:INPUT"Plan?(Y/N)";B$
124c123
< 1770 LOCATE 20,5:INPUT"ANOTHER(Y/N)  ";B$
---
> 1770 PRINT@220,"";:INPUT"ANOTHER(Y/N)  ";B$
153c152
< 2210 LOCATE 0,0:PRINT"NAME  TON   COST"
---
> 2210 PRINT@0,"NAME  TON   COST"
155,157c154,156
< 2230 LOCATE 1,L:PRINT CN$(I);:
< 2240 LOCATE 30,L:PRINT CT%(I);
< 2250 LOCATE 35,L:PRINT CC%(I);
---
> 2230 PRINT@1+(L*40),CN$(I);:
> 2240 PRINT@30+(L*40),CT%(I);
> 2250 PRINT@35+(L*40),CC%(I);
160c159
< 2280 LOCATE 0,7:PRINT"SELECT:U/D PAGE:L/R EDIT:ENT QUIT:ESC";
---
> 2280 PRINT@280,"SELECT:U/D PAGE:L/R EDIT:ENT QUIT:ESC";
173c172
< 2410 GOSUB 2480:INPUT"TONS:";A$:CT%(SE)=VAL(A$):FUEL%=VAL(A$)
---
> 2410 GOSUB 2480:INPUT"TONS:";A$:CT%(SE)=VAL(A$):IF SE=1 THEN FUEL%=VAL(A$)
175c174
< 2430 IF SE>30 THEN SE=30!SLE IF SE<1 THE SE=1
---
> 2430 IF SE>30 THEN SE=30 ELSE IF SE<1 THEN SE=1
180,181c179,180
< 2480 LOCATE 0,7:PRINT" ";
< 2490 LOCATE 0,7:RETURN
---
> 2480 PRINT@280," ";
> 2490 PRINT@280,"";:RETURN
183c182
< 2510 IF DIST*2 > FUEL% THEN LOCATE 20,4:PRINT"INSUFFICIENT FUEL";:LOCATE 
20,5:INPUT"";B$
---
> 2510 IF DIST*2 > FUEL% THEN PRINT@180,"INSUFFICIENT 
> FUEL";:PRINT@220,"";:INPUT"";B$

Re: [M100] Starship Management Software

[D10D3 Data]

I thought I wrote it to install the Line extension if it wasn't present,
but I guess I messed it up.

On Wed, Apr 8, 2020 at 8:09 PM John R. Hogerhuis  wrote:

>
>
> On Wed, Apr 8, 2020 at 4:09 PM Peter Vollan  wrote:
>
>> I think I have said before that if Virtual T "tokenises on the fly"
>> then it teaches us bad habits. And it makes no sense that it does this
>> for the m100 but not the NEC.
>>
>>
> So what? The habit is yours, break it.
>
>
>> BTW I am getting a syntax error from the first "LINE" statement.
>>
>>
> You need to install the LINE extension from web8201. It's not built-in.
>
> -- John.
>

Re: [M100] Starship Management Software

[John R. Hogerhuis]

On Wed, Apr 8, 2020 at 7:35 PM Brian K. White  wrote:

> On 4/8/20 10:00 PM, Mike Stein wrote:
> >
> > - Original Message -
> > From: "Brian K. White" 
> > To: 
> > Sent: Wednesday, April 08, 2020 9:53 PM
> > Subject: Re: [M100] Starship Management Software
> >
> >
> >> On 4/8/20 8:09 PM, John R. Hogerhuis wrote:
> >>>
> >>>
> >>> On Wed, Apr 8, 2020 at 4:09 PM Peter Vollan  >>> <mailto:dprogra...@gmail.com>> wrote:
> >>>
> >>>  I think I have said before that if Virtual T "tokenises on the
> fly"
> >>>  then it teaches us bad habits. And it makes no sense that it does
> this
> >>>  for the m100 but not the NEC.
> >>>
> >>>
> >>> So what? The habit is yours, break it.
> >>
> >> This sounds familiar.
> >>
> >
> > Sure does; give us a break and spare us another go-around.
>
> I await John's reaction to you telling him how to behave on his own mail
> list. ;)
>
>
I've given Mike "the business" on occasion :-)

But yeah this has already been discussed.

-- John.

Re: [M100] Starship Management Software

[Brian K. White]

On 4/8/20 10:00 PM, Mike Stein wrote:


- Original Message -
From: "Brian K. White" 
To: 
Sent: Wednesday, April 08, 2020 9:53 PM
Subject: Re: [M100] Starship Management Software



On 4/8/20 8:09 PM, John R. Hogerhuis wrote:



On Wed, Apr 8, 2020 at 4:09 PM Peter Vollan mailto:dprogra...@gmail.com>> wrote:

 I think I have said before that if Virtual T "tokenises on the fly"
 then it teaches us bad habits. And it makes no sense that it does this
 for the m100 but not the NEC.


So what? The habit is yours, break it.


This sounds familiar.



Sure does; give us a break and spare us another go-around.


I await John's reaction to you telling him how to behave on his own mail 
list. ;)


--
bkw

Re: [M100] Starship Management Software

[Mike Stein]

- Original Message - 
From: "Brian K. White" 
To: 
Sent: Wednesday, April 08, 2020 9:53 PM
Subject: Re: [M100] Starship Management Software


> On 4/8/20 8:09 PM, John R. Hogerhuis wrote:
>> 
>> 
>> On Wed, Apr 8, 2020 at 4:09 PM Peter Vollan > <mailto:dprogra...@gmail.com>> wrote:
>> 
>> I think I have said before that if Virtual T "tokenises on the fly"
>> then it teaches us bad habits. And it makes no sense that it does this
>> for the m100 but not the NEC.
>> 
>> 
>> So what? The habit is yours, break it.
> 
> This sounds familiar.
> 
> -- 
> bkw

Sure does; give us a break and spare us another go-around.

Re: [M100] Starship Management Software

[Brian K. White]

On 4/8/20 8:09 PM, John R. Hogerhuis wrote:



On Wed, Apr 8, 2020 at 4:09 PM Peter Vollan > wrote:


I think I have said before that if Virtual T "tokenises on the fly"
then it teaches us bad habits. And it makes no sense that it does this
for the m100 but not the NEC.


So what? The habit is yours, break it.


This sounds familiar.

--
bkw

Re: [M100] Starship Management Software

[John R. Hogerhuis]

On Wed, Apr 8, 2020 at 4:09 PM Peter Vollan  wrote:

> I think I have said before that if Virtual T "tokenises on the fly"
> then it teaches us bad habits. And it makes no sense that it does this
> for the m100 but not the NEC.
>
>
So what? The habit is yours, break it.


> BTW I am getting a syntax error from the first "LINE" statement.
>
>
You need to install the LINE extension from web8201. It's not built-in.

-- John.

Re: [M100] Starship Management Software

[Peter Vollan]

I think I have said before that if Virtual T "tokenises on the fly"
then it teaches us bad habits. And it makes no sense that it does this
for the m100 but not the NEC.

BTW I am getting a syntax error from the first "LINE" statement.

On Wed, 8 Apr 2020 at 13:52, John R. Hogerhuis  wrote:
>
> As a general practice it's better to name files as ASCII files as .DO and 
> tokenized files as .BA
>
> Otherwise you rely on the fallback mechanisms. I guess VirtualT just 
> tokenizes the file on-the-fly. But it doesn't work for NEC.
>
> LaddieAlpha's fallback mechanism is just to present the file with the correct 
> extension depending on tell-tale binary content in tokenized files. But now 
> that you point it out, I haven't tried it with NEC so who knows. I'd give it 
> a 90% chance of doing the right thing.
>
> -- John.

Re: [M100] Starship Management Software

[John R. Hogerhuis]

As a general practice it's better to name files as ASCII files as .DO and
tokenized files as .BA

Otherwise you rely on the fallback mechanisms. I guess VirtualT just
tokenizes the file on-the-fly. But it doesn't work for NEC.

LaddieAlpha's fallback mechanism is just to present the file with the
correct extension depending on tell-tale binary content in tokenized files.
But now that you point it out, I haven't tried it with NEC so who knows.
I'd give it a 90% chance of doing the right thing.

-- John.

Re: [M100] Starship Management Software

[Ken Pettit]

Hey Everyone,

In VirtualT, the NEC direct load of a tokenized .BA doesn't work 
correctly because the tokenizer in NEC is different than 
M100/T102/T200.  I don't know if that is what you are trying to do or not.


To load into NEC, you would have to load a non-tokenized .DO file, then 
load the .DO from BASIC and let the NEC native ROM tokenizer do the work.


Ken

On 4/8/20 1:12 PM, Peter Vollan wrote:

Attempting to run your program in Virtual T, it seems that the 8201
emulation is not working. Not only does it hang when I try to load the
program, but the function key labels do not line up properly. I am
using 1.7.

On Tue, 7 Apr 2020 at 01:59, Tom Wilson  wrote:

That's a great idea! Now I want to see a group of gamers sitting around a 
table, using their Model T computers to manage their character sheets


Tom Wilson
wilso...@gmail.com
(619)940-6311
K6ABZ


On Mon, Apr 6, 2020 at 3:11 PM D10D3 Data  wrote:

I wrote a utility on my NEC 8201A to aid the players in a scifi RPG I run. If 
anyone is curious I've posted the code here:  https://pastebin.com/9EJ7JbDN
It's NEC basic, so it won't run on an M100 without a bit of porting, but if you 
have a NEC or run Virtual-T in NEC mode you can try it out. It's janky and far 
from optimized but it works.
-Jason

Re: [M100] Starship Management Software

[Peter Vollan]

Okay, now I've got it. The NEC emulation cannot load a text file as a
basic program as the m100 emulation does, it must have the .do
extension and then be converted.


On Wed, 8 Apr 2020 at 13:12, Peter Vollan  wrote:
>
> Attempting to run your program in Virtual T, it seems that the 8201
> emulation is not working. Not only does it hang when I try to load the
> program, but the function key labels do not line up properly. I am
> using 1.7.
>
> On Tue, 7 Apr 2020 at 01:59, Tom Wilson  wrote:
> >
> > That's a great idea! Now I want to see a group of gamers sitting around a 
> > table, using their Model T computers to manage their character sheets
> >
> >
> > Tom Wilson
> > wilso...@gmail.com
> > (619)940-6311
> > K6ABZ
> >
> >
> > On Mon, Apr 6, 2020 at 3:11 PM D10D3 Data  wrote:
> >>
> >> I wrote a utility on my NEC 8201A to aid the players in a scifi RPG I run. 
> >> If anyone is curious I've posted the code here:  
> >> https://pastebin.com/9EJ7JbDN
> >> It's NEC basic, so it won't run on an M100 without a bit of porting, but 
> >> if you have a NEC or run Virtual-T in NEC mode you can try it out. It's 
> >> janky and far from optimized but it works.
> >> -Jason

Re: [M100] Starship Management Software

[Peter Vollan]

Attempting to run your program in Virtual T, it seems that the 8201
emulation is not working. Not only does it hang when I try to load the
program, but the function key labels do not line up properly. I am
using 1.7.

On Tue, 7 Apr 2020 at 01:59, Tom Wilson  wrote:
>
> That's a great idea! Now I want to see a group of gamers sitting around a 
> table, using their Model T computers to manage their character sheets
>
>
> Tom Wilson
> wilso...@gmail.com
> (619)940-6311
> K6ABZ
>
>
> On Mon, Apr 6, 2020 at 3:11 PM D10D3 Data  wrote:
>>
>> I wrote a utility on my NEC 8201A to aid the players in a scifi RPG I run. 
>> If anyone is curious I've posted the code here:  
>> https://pastebin.com/9EJ7JbDN
>> It's NEC basic, so it won't run on an M100 without a bit of porting, but if 
>> you have a NEC or run Virtual-T in NEC mode you can try it out. It's janky 
>> and far from optimized but it works.
>> -Jason

Re: [M100] Starship Management Software

[Tom Wilson]

That's a great idea! Now I want to see a group of gamers sitting around a
table, using their Model T computers to manage their character sheets


Tom Wilson
wilso...@gmail.com
(619)940-6311
K6ABZ


On Mon, Apr 6, 2020 at 3:11 PM D10D3 Data  wrote:

> I wrote a utility on my NEC 8201A to aid the players in a scifi RPG I run.
> If anyone is curious I've posted the code here:
> https://pastebin.com/9EJ7JbDN
> It's NEC basic, so it won't run on an M100 without a bit of porting, but
> if you have a NEC or run Virtual-T in NEC mode you can try it out. It's
> janky and far from optimized but it works.
> -Jason
>