flashjazzcat Posted June 24, 2023 Share Posted June 24, 2023 1 hour ago, drac030 said: The files on CAR: are not (and have never been) executed in-place. They are copied to RAM. The system sees them as normal file streams, thus a "read" means copying data from the media (cartridge banks) to the operating memory (per usual rules). This was assumed from the outset, but (pertinent to the earlier discussion), does the open function perform filename matching in-situ (ROM), or first copy the directory data to a buffer and then perform the filename match? 1 Quote Link to comment Share on other sites More sharing options...
drac030 Posted June 24, 2023 Share Posted June 24, 2023 32 minutes ago, flashjazzcat said: does the open function perform filename matching in-situ (ROM), or first copy the directory data to a buffer and then perform the filename match? The open function first opens and reads the directory, so the file name matching is performed in the RAM buffer. 1 1 Quote Link to comment Share on other sites More sharing options...
Faicuai Posted June 25, 2023 Share Posted June 25, 2023 (edited) 7 hours ago, drac030 said: 3) The files on CAR: are not (and have never been) executed in-place. They are copied to RAM. The system sees them as normal file streams, thus a "read" means copying data from the media (cartridge banks) to the operating memory (per usual rules). I can clearly see that with MAN files... I tried my own medicine here, so I issued a "MAN COPY" command which I aborted shortly after via BRK key. Went to HD active directory at that moment, and found a .TMP file with the ENTIRE (and de-compressed) content of SDX's rom-disk matching MAN file !! 🥴 BUT... I noticed that when issuing a "CAR:" command, and then issuing a "ARC", "FIND", 'MENU', "FDISK', directly on CAR: device path, the response was almost INSTANT. Some of those commands are larger in size, and also run with .OVL files (not shown in DIR CAR: command). How come they run THAT fast while somehow being copied to RAM first? That is quite a feat, there. Edited June 25, 2023 by Faicuai Quote Link to comment Share on other sites More sharing options...
hueyjones70 Posted July 9, 2023 Share Posted July 9, 2023 Where can I find an ATR of RealDOS and SpartaDOS. Nevermind, I found them. Quote Link to comment Share on other sites More sharing options...
drac030 Posted August 3, 2023 Share Posted August 3, 2023 On 6/25/2023 at 6:35 AM, Faicuai said: How come they run THAT fast while somehow being copied to RAM first? That is quite a feat, there. Sorry, I overlooked your post. The answer is that real disks (and RAM-disks too) are split into fixed-size sectors, which must be buffered. If you want to read 1 byte from a disk file, it first involves reading a sector into a sector buffer, then your byte is fetched from there and copied into your destination. Even if the data are already in the buffer (so no disk access is necessary), it is still relatively expensive. CAR:, on the other hand, is not organized into sectors, so any amount of data may be directly copied into the destination memory without any intermediate buffers and associated copying operations. 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.