Upgrading from MDOS 0.97R to 6.50

[webdeck]

I have tried upgrading from MDOS 0.97R to 6.50, but none of my programs run.  They all give me the error "Bad command or filename."

 

Do I need to change something in my AUTOEXEC file?  Here is what I have:

timode
echo off
mode RS232/1:1200,N,8,1
mode RS232/2:9600,N,8,1
mode 80
ramdisk 90
prompt $t$b$n:\$p$g
assign d=DSK5:
path e:\SYS;e:\SYS\BATCH;d:
e:
cd \SYS
chkdsk e:
ver

 

[+Ksarul]

One note: have you added the additional 32K RAM modification? You need it for any MDOS version after 2.50. . .

[webdeck]

13 minutes ago, Ksarul said:

One note: have you added the additional 32K RAM modification? You need it for any MDOS version after 2.50. . .

Yes, I have that installed.

 

chkdsk reports 589824 bytes of total memory, 90112 bytes free

[+InsaneMultitasker]

Examples of programs that aren't running...?

 

MDOS was intentionally volatile at the time, with certain page numbers and routines changing between releases.

 

Are your filenames lower case? MDOS 6.50 has a 'case' command that converts filenames to upper case.

 

What device names are you using?   Hard drive is now "HDSx" not "WDSx" in MDOS

 

type REMAP and ASSIGN at the command line and share.

[webdeck]

Ah!  "case on" is the thing I needed to do!

 

One other question - I tried editing AUTOEXEC using MyWord and it looks like it added a line of garbage at the end of the file.  Is that a bug or is there something I need to do in MyWord to prevent that from happening?

 

 

[+mizapf]

Why are you using timode for the autoexec? Doesn't this take away resources for native applications?

 

(I'm using timode only in scripts that launch GPL mode, or for EXEC.)

[+InsaneMultitasker]

1 minute ago, webdeck said:

Ah!  "case on" is the thing I needed to do!

 

One other question - I tried editing AUTOEXEC using MyWord and it looks like it added a line of garbage at the end of the file.  Is that a bug or is there something I need to do in MyWord to prevent that from happening?

 

 

That's the tab info, common with TI Writer, Funnelweb, etc.  Flip to Program Edit (PE) mode and/or save using the PrintFile (PF) option.

 

There are a few native MDOS editors.  I prefer "EDIT" by P. Muys for all of my programming.  There is also one called QDE by C. Pulley.  Some other programs you might want to grab along the way :

Directory Manager - native MDOS file manager

EXEC - loads EA Option 5 programs from the command line

 

[webdeck]

11 minutes ago, mizapf said:

Why are you using timode for the autoexec? Doesn't this take away resources for native applications?

 

(I'm using timode only in scripts that launch GPL mode, or for EXEC.)

In the olden days, timode had to be the first line of the AUTOEXEC if you wanted the option to run gpl.  Is that no longer the case?

[+mizapf]

I'm using a script like this:

 

STDEA:

TIMODE
ECHO Loading GPL Interpreter & Standard EA
GPL EA

 

and run it as &STDEA. (Ampersand causes a warm reboot.)

Edited December 12, 2020 by mizapf

[+9640News]

2 hours ago, webdeck said:

Ah!  "case on" is the thing I needed to do!

 

One other question - I tried editing AUTOEXEC using MyWord and it looks like it added a line of garbage at the end of the file.  Is that a bug or is there something I need to do in MyWord to prevent that from happening?

 

 

I think use Program Edit mode of MyWord.

 

[webdeck]

10 hours ago, mizapf said:

I'm using a script like this:

 

STDEA:

TIMODE
ECHO Loading GPL Interpreter & Standard EA
GPL EA

 

and run it as &STDEA. (Ampersand causes a warm reboot.)

Great tip - thanks!