You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Disc Image Manager loads the entire disc image into memory then works on it from there. This is fine for speed, and for floppy images and most RISC OS and AmigaDOS hard disc images. But for bigger images - RISC OS 4.39 could access a 40GB drive, while the latest, 5.28, can access much bigger drives, particularly on a Raspberry Pi. This leaves this application open for a crash should it be presented with a file much bigger than memory allows.
The other advantage to streaming the disc image is that the application can access what it needs, much like a floppy or hard drive head in a physical machine.
The text was updated successfully, but these errors were encountered:
Currently Disc Image Manager loads the entire disc image into memory then works on it from there. This is fine for speed, and for floppy images and most RISC OS and AmigaDOS hard disc images. But for bigger images - RISC OS 4.39 could access a 40GB drive, while the latest, 5.28, can access much bigger drives, particularly on a Raspberry Pi. This leaves this application open for a crash should it be presented with a file much bigger than memory allows.
The other advantage to streaming the disc image is that the application can access what it needs, much like a floppy or hard drive head in a physical machine.
The text was updated successfully, but these errors were encountered: