Jump to content

Recommended Posts

Is there a reason that RespeQt 5.1 can't mount a CP/M disk as B: (D2:)? I want to check out WordStar with my Indus. ATR attached.

 

WordStar - CPM 80.ATR

Share this post


Link to post
Share on other sites

If the latest version (5.3) does not work, please try a legacy version (4) from jzatarski to check if this is a regression or if it never worked.

Share this post


Link to post
Share on other sites

I don't know how I ended up with 5.1. I thought it was 5.3 on that computer. If the ATR is bad, does anyone know where a good one is?

Thanks.

 

Share this post


Link to post
Share on other sites

I have 5.3 now. It stops emulation (seemingly randomly) when I am using CP/M. I had to turn off all highspeed stuff. I was playing Zork and still got BDOS Err on B: a few times.

Is there a way to configure @trub Term (TT) to use high speed, or is the Indus directly commanding B:?

There has got to be a way to make this nice and fast.

 

Ideally, we should be able to have the Atari -> Indus -> Atari speed made faster, and allow PBI mounted images to be used as B: instead of slow SIO.

 

Any suggestions?

 

Share this post


Link to post
Share on other sites

All it would take is a DCB change in the BIOS to support larger drives, as well.

There is much room for improvement.

 

Share this post


Link to post
Share on other sites
3 hours ago, Kyle22 said:

I have 5.3 now. It stops emulation (seemingly randomly) when I am using CP/M. I had to turn off all highspeed stuff

Do you mean that with version 5.1, it was working well without turning off all highspeed stuff?

Share this post


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

Do you mean that with version 5.1, it was working well without turning off all highspeed stuff?

No, AFAIK, the version doesn't matter. This needs more testing. I was using Trub Terminal.

 

Share this post


Link to post
Share on other sites

@Kyle22, did you try the latest version that fixed some flashing and size issues?

maybe something has improved?

@ebiguy, what's the direct link to the latest version, and can you describe the fixes that were included?

Share this post


Link to post
Share on other sites
6 hours ago, _The Doctor__ said:

what's the direct link to the latest version, and can you describe the fixes that were included?

There is no link because there is no binary built yet.

I am waiting for the latest code (printer emulation) from Jochen.

We will have a call this week-end.

Then I will also make a couple of fixes in the 1020 printer emulation.

And finally, we will be able to release a 5.4 with better printing emulation and the fix about the ATR size issue.

Nothing else is planned.

  • Like 1

Share this post


Link to post
Share on other sites
4 hours ago, ebiguy said:

There is no link because there is no binary built yet.

I am waiting for the latest code (printer emulation) from Jochen.

We will have a call this week-end.

Then I will also make a couple of fixes in the 1020 printer emulation.

And finally, we will be able to release a 5.4 with better printing emulation and the fix about the ATR size issue.

Nothing else is planned.

I hope that once FujiNet becomes more widely known and people become more familiar with its code and features that the amazing printer emulation features can be ported over into RespeQt. It would be amazing to have that kind of Epson emulation in the hands of RespeQt users.

 

EDIT: Apologies for the thread hijack! I forgot what the thread topic was when I replied.

  • Like 3

Share this post


Link to post
Share on other sites
On 6/25/2020 at 4:24 AM, Kyle22 said:

Is there a way to configure @trub Term (TT) to use high speed, or is the Indus directly commanding B:?

TT simply calls SIOV OS procedure to access the B: drive, so the speed depends on OS.

You get high speed if OS itself supports this or if the high speed handler is hooked to the OS vector (such as SIO driver in the FJC's Ultimate1MB firmware).

However, after reading the data, TT still needs to send it to Indus CP/M via SIO. A double transfer is then needed: drive B: -> TT -> Indus CP / M, which results in poor performance.

Share this post


Link to post
Share on other sites

@trub So this should in theory work with a PBI HD partition as B: then? I wonder if the DPB can be patched to use more than a 180K disk.

 

 

Share this post


Link to post
Share on other sites
28 minutes ago, _The Doctor__ said:

almost sounds like the CP/M sio routine in the indus needs a patch when in cp/m mode.

To do more than 19,200 yeah. Divisor zero would be SWEET!

 

Goal: Get NZ-COM on the Indus. Use fast SIO and PBI large HD image as B:

 

Edited by Kyle22
clarity

Share this post


Link to post
Share on other sites
21 hours ago, Kyle22 said:

@trub So this should in theory work with a PBI HD partition as B: then? I wonder if the DPB can be patched to use more than a 180K disk.

Sure it can be done. However, I think it would be better to patch DPB for drive C (it now set for 90k disk in the second drive, so of questionable use nowadays).

Share this post


Link to post
Share on other sites

Sure. Drive 'C:' would be nice. There has got to be a way to make it a pleasure instead of a chore to use WordStar.

 

:)

 

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.
Note: Your post will require moderator approval before it will be visible.

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...