Search found 2833 matches
- Mon May 13, 2013 7:17 pm
- Forum: ADFFS
- Topic: ADFFS's SWI handler
- Replies: 3
- Views: 3973
ADFFS's SWI handler
I've noticed the ADFFS Filer fails horribly on a 32bit OS now which I'm certain is caused by the SWI dispatcher on ADFFS...hence this thread on TIB.
- Mon May 13, 2013 7:10 pm
- Forum: ADFFS
- Topic: DA in Application space on a 16mb RO3.1 machine
- Replies: 3
- Views: 4410
Re: DA in Application space on a 16mb RO3.1 machine
Right...the plan is: All calls to OS_DynamicArea (0) must have R5 set (maximum size of area) or they'll be rejected. OS_DynamicArea will then map memory away if required to ensure there's no memory in the area, which ends at the 16mb boundary and grows downwards by maximum area size on each DA alloc...
- Mon May 13, 2013 6:57 pm
- Forum: ADFFS
- Topic: DA in Application space on a 16mb RO3.1 machine
- Replies: 3
- Views: 4410
Re: DA in Application space on a 16mb RO3.1 machine
Humm, that'll use 4Mb of someone's nice 16Mb machine... Ah well, I suppose they can afford it ;-) Only 2mb, as it will reduce the RO DA after it's allocated to ADFFS. And even then, it will only need to do this if 2mb hasn't already been allocated. The only reason to allocate the memory in this way...
- Mon May 13, 2013 6:32 pm
- Forum: ADFFS
- Topic: Extending RO3.1 OS_DynamicArea
- Replies: 13
- Views: 15108
Re: Extending RO3.1 OS_DynamicArea
Thanks for confirming, I'll go add the checks using OS_ReadMemMapInfo
- Mon May 13, 2013 6:07 pm
- Forum: ADFFS
- Topic: Extending RO3.1 OS_DynamicArea
- Replies: 13
- Views: 15108
Re: Extending RO3.1 OS_DynamicArea
Do we know anyone with 3/4 MEMC's?
ps I'll get recoding OS_DynamicArea to support multiple DA's, which give you a few weeks to integrate the latest LCDgm
ps I'll get recoding OS_DynamicArea to support multiple DA's, which give you a few weeks to integrate the latest LCDgm
- Mon May 13, 2013 6:12 am
- Forum: AutoVIDC
- Topic: AutoVIDC 2.08 available for testing
- Replies: 11
- Views: 16978
Re: AutoVIDC 2.08 available for testing
I've dropped in into ADFFS and will do some testing during the week.
In the !Run I'm simply checking if AutoVIDC is loaded and forcing it if not. Should I also be checking the version number and reloading if an older one is present?
In the !Run I'm simply checking if AutoVIDC is loaded and forcing it if not. Should I also be checking the version number and reloading if an older one is present?
- Mon May 13, 2013 6:05 am
- Forum: ADFFS
- Topic: Extending RO3.1 OS_DynamicArea
- Replies: 13
- Views: 15108
Re: Extending RO3.1 OS_DynamicArea
Does that still work with additional MEMC chips? I don't have one to confirm. The page counter in RO 3.1 is a byte value, which by my reckoning limits it to 8192KB with 32KB pages. How does it deal with 3 MEMC's? I'd say several modules would need to be updated before before additional MEMC's would ...
- Sat May 11, 2013 8:05 am
- Forum: ADFFS
- Topic: Hanging when shelling out with 1.6MB floppy mounted
- Replies: 8
- Views: 6980
Re: Hanging when shelling out with 1.6MB floppy mounted
I've been looking into the hanging on RO3.5 this morning, from recording what happens when the WIMP shuts down, things happen slightly differently if an F format floppy is mounted: E Format: 1. MiscOp 5 is called to eject the floppy F Format: 1. MiscOp 1 is called to see if the floppy has changed 2....
- Sat May 11, 2013 7:25 am
- Forum: ADFFS
- Topic: Extending RO3.1 OS_DynamicArea
- Replies: 13
- Views: 15108
Extending RO3.1 OS_DynamicArea
As DA's are now in application space, I could extend OS_DynamicArea to support multiple DA's. The only caveat being pre-allocating each DA to it's maximum size on machines where there could be the possibility of a DA conflicting with Application space. For example, if two DA's are allocated they map...
- Sat May 11, 2013 7:17 am
- Forum: ADFFS
- Topic: DA in Application space on a 16mb RO3.1 machine
- Replies: 3
- Views: 4410
DA in Application space on a 16mb RO3.1 machine
Pre-allocating memory when there's more than 14mb in Application space isn't straight forward, due to the overlapping address space. A possible solution is: Increase an official RO DA to 2mb (to ensure the top 2mb of application space isn't mapped) Allocate 2mb to ADFFS Decrease RO DA back to it's o...