Jump to content
jedimatt42

I need a new users guide to MDOS and the last 35 years

Recommended Posts

7 hours ago, BeeryMiller said:

Does Form 1.23 show the CRU at >1x00, or >1x01?  Is it an even, or odd address?

 

hmmmmm now where you ask, yesterday I stumbled about that. I did not see the ramdisk with the DU2K-utulity,

while looking for the HFDC´s DSRs. Is this normal ? 

 

I slightly remember that there was shown an >1401 while formatting days ago,

but ALSO remember the >1400 at some other situation.... (maybe)

 

I will crush the ramdisk tonight (logically) :) and will try again to see what is shown, with FORM3MEG and then finally with FORM123...

 

 

Share this post


Link to post
Share on other sites
7 hours ago, Schmitzi said:

 

hmmmmm now where you ask, yesterday I stumbled about that. I did not see the ramdisk with the DU2K-utulity,

while looking for the HFDC´s DSRs. Is this normal ? 

 

I slightly remember that there was shown an >1401 while formatting days ago,

but ALSO remember the >1400 at some other situation.... (maybe)

 

I will crush the ramdisk tonight (logically) :) and will try again to see what is shown, with FORM3MEG and then finally with FORM123...

 

 

On the Geneve, there will not be a DSR on the card for the ramdisk as the DSR is part of the Geneve Master DSR.


Make sure when you use DU2K, it is with ROMPAGE ON.

 

Beery

  • Like 1

Share this post


Link to post
Share on other sites

@BeeryMiller

 

I investigated the ASSIGN issue some more now. (could not ASSIGN a driveletter to HRD3000 1.5MB )

 

This was under MDOS5.0, and now under MDOS6.50  it works (just booted it from disk).

I can assign drive letter F:  (but not N:) and that´s OK for me for the moment.

So I think there is no need to FORM123 the drive again (and make it smaller)

 

Ah, and I checked both, FORM123 and FORM3MEG, and both show up >1400 (not: >1401),

and the option to choose the HRD as 8-bit or as 16-bit. I am sure I choosed FORM3MEG and "16-bit" some weeks ago.

Somewhere around I saw that N: is the "natural given" driveletter for that.

Maybe mapping to N: (tells me "Device error") needs some LASTDRIVE command in AUTOEXEC, or whatever,

but this command does not work at all. But no problem, all solved for me at the moment, it works,

I have a driveletter for easy handling, and will reformat and reconfigure it all when my IDE and the new MDOS7.20 arrive.

So no more need to tinker with interims.

thx a lot :thumbsup:

 

 

 

  • Like 3

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...