Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.apple2.programmer > #3887 > unrolled thread

Query about ProDOS 8

Back to article view | Back to comp.sys.apple2.programmer

Contents

  Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-02 15:17 +0000
    Re: Query about ProDOS 8 John Brooks <jbrooks@blueshiftinc.com> - 2017-09-02 09:35 -0700
      Re: Query about ProDOS 8 James Davis <JPD.Enterprises@outlook.com> - 2017-09-02 12:20 -0700
      Re: Query about ProDOS 8 ol.sc@web.de (Oliver Schmidt) - 2017-09-08 10:53 +0000
        Re: Query about ProDOS 8 John Brooks <jbrooks@blueshiftinc.com> - 2017-09-11 21:53 -0700
          Re: Query about ProDOS 8 Steve Nickolas <usotsuki@buric.co> - 2017-09-12 03:51 -0400
            Re: Query about ProDOS 8 David Schmenk <dschmenk@gmail.com> - 2017-09-12 06:59 -0700
          Re: Query about ProDOS 8 ol.sc@web.de (Oliver Schmidt) - 2017-09-12 14:41 +0000
          Re: Query about ProDOS 8 Michael J. Mahon <mjmahon@aol.com> - 2017-09-12 11:18 -0500
    Re: Query about ProDOS 8 roger.shimada@gmail.com - 2017-09-02 10:48 -0700
    Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-02 20:34 +0000
      Re: Query about ProDOS 8 roger.shimada@gmail.com - 2017-09-02 20:35 -0700
        Re: Query about ProDOS 8 John Brooks <jbrooks@blueshiftinc.com> - 2017-09-02 21:47 -0700
          Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-03 09:34 +0000
            Re: Query about ProDOS 8 David Schmenk <dschmenk@gmail.com> - 2017-09-03 07:15 -0700
              Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-03 16:12 +0000
            Re: Query about ProDOS 8 John Brooks <jbrooks@blueshiftinc.com> - 2017-09-04 22:00 -0700
              Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-05 09:13 +0000
              Re: Query about ProDOS 8 James Davis <JPD.Enterprises@outlook.com> - 2017-09-06 17:56 -0700
                Re: Query about ProDOS 8 John Brooks <jbrooks@blueshiftinc.com> - 2017-09-07 00:00 -0700
              Re: Query about ProDOS 8 Steve Nickolas <usotsuki@buric.co> - 2017-09-10 23:30 -0400
                Re: Query about ProDOS 8 David Schmenk <dschmenk@gmail.com> - 2017-09-11 06:52 -0700
        Re: Query about ProDOS 8 roger.shimada@gmail.com - 2017-09-03 07:05 -0700
    Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-02 20:37 +0000
      Re: Query about ProDOS 8 Antoine Vignau <antoine.vignau@laposte.net> - 2017-09-02 14:07 -0700
    Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-02 21:36 +0000
    Re: Query about ProDOS 8 James Davis <JPD.Enterprises@outlook.com> - 2017-09-03 18:45 -0700
      Re: Query about ProDOS 8 Antoine Vignau <antoine.vignau@laposte.net> - 2017-09-03 23:52 -0700
    Re: Query about ProDOS 8 Jorge <jorge@jorgechamorro.com> - 2017-09-12 13:42 -0700
      Re: Query about ProDOS 8 ol.sc@web.de (Oliver Schmidt) - 2017-09-13 10:30 +0000
        Re: Query about ProDOS 8 Steven Hirsch <snhirsch@gmail.com> - 2017-09-13 08:00 -0400
        Re: Query about ProDOS 8 Jorge <jorge@jorgechamorro.com> - 2017-09-14 07:30 -0700

Page 2 of 2 — ← Prev page 1 [2]

#3920

[Multipart message — attachments visible in raw view] — view raw

On Mon, 4 Sep 2017, John Brooks wrote:

> Yes, my current in-progress driver has both a min-bank and max-bank 
> parameter which is used at boot to set up the size of the /RAM3 drive. 
> These values are currently set to 1 and the max bank found by scanning 
> the Ramworks banks, but my intent is to allow them to be adjusted for 
> Appleworks and other 'big aux mem' applications.
>
> However, since bank assignment is a boot-time decision, I do not have a 
> good idea on the API/approach to use to allow these parameters to be 
> adjusted. Any ideas on how you'd like to see aux-mem banks reserved?

My own opinion would be, a text configuration file in the root of the boot 
drive could be used to set boot-time parameters, à la MS-DOS 2.0+ and 
CONFIG.SYS, but maybe that's a little overkill for a poor yickle 
8-bitter...

-uso.

[toc] | [prev] | [next] | [standalone]

#3924

On Sunday, 10 September 2017 20:30:04 UTC-7, Steve Nickolas  wrote:
> On Mon, 4 Sep 2017, John Brooks wrote:
> 
> > Yes, my current in-progress driver has both a min-bank and max-bank 
> > parameter which is used at boot to set up the size of the /RAM3 drive. 
> > These values are currently set to 1 and the max bank found by scanning 
> > the Ramworks banks, but my intent is to allow them to be adjusted for 
> > Appleworks and other 'big aux mem' applications.
> >
> > However, since bank assignment is a boot-time decision, I do not have a 
> > good idea on the API/approach to use to allow these parameters to be 
> > adjusted. Any ideas on how you'd like to see aux-mem banks reserved?
> 
> My own opinion would be, a text configuration file in the root of the boot 
> drive could be used to set boot-time parameters, à la MS-DOS 2.0+ and 
> CONFIG.SYS, but maybe that's a little overkill for a poor yickle 
> 8-bitter...
> 
> -uso.

I'd actually like to see installable device drivers along with a configuration file. It starts to look a little like SOS at some point.

[toc] | [prev] | [next] | [standalone]

#3901

On Saturday, September 2, 2017 at 10:35:39 PM UTC-5, roger....@gmail.com wrote:
> On Saturday, September 2, 2017 at 3:39:13 PM UTC-5, Benoit0123 wrote:
> > I got a "crash" as a ProDOS device was read from an
> > interrupt routine while the mini assembler was active. This is on an
> > Enhanced Apple //e.
> 
> Short answer: Try saving and restoring $44 in your interrupt handling routine.

After further thought and code review, I don't think that will make a difference.

$44 will contain the machine state on a BRK instruction. For an IRQ, the firmware is pushing the machine state on the stack.

Try saving and restoring the zero page locations that John Brooks mentioned.

[toc] | [prev] | [next] | [standalone]

#3893

Oops: typo: please read $FBB4 instead of $FFB4 in my previous message.
Benoît

[toc] | [prev] | [next] | [standalone]

#3894

Why do you use BI 1.1 in ProDOS 2.4.1?

[toc] | [prev] | [next] | [standalone]

#3895

Reply to last message from Antoine.

Hello Antoine,

How did you find that I am using BI 1.1 for the time being? ;-)
I am using BI 1.1 and not BI 1.6 because I have an assembly listing for BI
1.1 on hand, thing that I have not for more modern BI version (cf. Sandy
Mossberg's column in Nibble magazine: I've typed in the whole series into
Merlin Pro then 8 in a past life).
I might be wrong but I believe that the release notes between successive BI
version from 1.0/1.1 up to latest 1.6 form only a quite thin document
(reduced # of A4 pages) ;-). but I need to get the same absolute addressing
between the paper listing and the electronic image of this system file for
the time being.
I do not think that the BI plays an active role (either positive or
negative) for the issue I've described here (again I might be wrong...)

Best regards,
Benoît



-- 
Growing old is mandatory..
growing up is optional..
But the other way round is as true.

[toc] | [prev] | [next] | [standalone]

#3906

Don't know anything about this subject, but, at the risk of "sticking my foot in my mouth" again, and because not everyone always thinks of the obvious things, I'll put in my two cents, too. 

After reading this thread up to this point, I wonder: 

1) if you have tried using a fully qualified pathname; and 

2) while analyzing the Old Monitor ROM, I came across this warning about the Old DOS--from What's Where in the Apple--but it might not be true for ProDOS: 

(My "Apple II Equates" version) 
STATUS   EQU $48   ;[OM] USER P-REG (AKA: STATUS REGISTER): SAVED HERE 
                   ;     ON BRK TO MONITOR & DURING TRACE & BY MONITOR 
                   ;     SAVE ROUTINE; WARNING: INITIALIZE BEFORE MON-
                   ;     ITOR GOTO (G) FUNCTION TO AVOID DECIMAL MODE 
                   ;     IF DOS HAS BEEN USED.

Hope this helps, 

James Davis 

[toc] | [prev] | [next] | [standalone]

#3907

The meaning is the same under all revisions. From the GS firmware equates:

STATUS		EQU	$48	;P reg after break 

av

[toc] | [prev] | [next] | [standalone]

#3931

I have no idea how ProDos works, but IIRC what CP/M did was allow you to overwrite almost everything except the very bare minimum required (a few kb) for the io vectors to work, so that if you wanted to use a lot of memory you could, then only had to exit with a JMP to a warm "reboot" (IIRC at ($0)) instead of ending via an RTS.

-- 
Jorge.

[toc] | [prev] | [next] | [standalone]

#3932

Hi Jorge,

>I have no idea how ProDos works, but IIRC what CP/M did was allow you to ov=
>erwrite almost everything except the very bare minimum required (a few kb) =
>for the io vectors to work, so that if you wanted to use a lot of memory yo=
>u could, then only had to exit with a JMP to a warm "reboot" (IIRC at ($0))=
> instead of ending via an RTS.

If you'd replace the default ProDOS selector/exit code with one that
without any user interaction goes ahead and loads BASIC.SYSTEM you'd
end up with basically the same approach:

- Smaller (BIN) programs keep the shell in RAM (and exit via DOS
WARM).
- Larger (SYS) programs replace the shell and have it reloaded (by
exiting via ProDOS QUIT).

Regards,
Oliver

[toc] | [prev] | [next] | [standalone]

#3933

On 09/13/2017 06:30 AM, Oliver Schmidt wrote:
> Hi Jorge,
> 
>> I have no idea how ProDos works, but IIRC what CP/M did was allow you to ov=
>> erwrite almost everything except the very bare minimum required (a few kb) =
>> for the io vectors to work, so that if you wanted to use a lot of memory yo=
>> u could, then only had to exit with a JMP to a warm "reboot" (IIRC at ($0))=
>> instead of ending via an RTS.

> If you'd replace the default ProDOS selector/exit code with one that
> without any user interaction goes ahead and loads BASIC.SYSTEM you'd
> end up with basically the same approach:
> 
> - Smaller (BIN) programs keep the shell in RAM (and exit via DOS
> WARM).
> - Larger (SYS) programs replace the shell and have it reloaded (by
> exiting via ProDOS QUIT).

Many years ago I worked with others on a 9 Mhz. Z180 based coprocessor board.
The 6502 BIOS portion of CardZ180 CP/M was actually a ProDOS system program. 
the ProDOS kernel stayed resident and allowed CP/M programs to read and write 
ProDOS files.

[toc] | [prev] | [next] | [standalone]

#3935

On Wednesday, September 13, 2017 at 12:30:20 PM UTC+2, Oliver Schmidt wrote:
> 
> If you'd replace the default ProDOS selector/exit code with one that
> without any user interaction goes ahead and loads BASIC.SYSTEM you'd
> end up with basically the same approach:
> 
> - Smaller (BIN) programs keep the shell in RAM (and exit via DOS
> WARM).
> - Larger (SYS) programs replace the shell and have it reloaded (by
> exiting via ProDOS QUIT).

Hi Oliver,

That sounds good! (I guess)

But I have made a 2.4.1 disk with ADTPro :-) and it takes 10.5s to boot into BASIC.SYSTEM. I have done the same with ESDOS and it boots in 4.5s. So... I still don't like ProDOS :-)

Please see what I've said of the cassette/audio transfers in c.s.a2, in the thread "What did an original Apple II sell for?"

Regards,
-- 
Jorge.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.sys.apple2.programmer

csiph-web