leonard wrote:The kernel use low memory, and it's not compatible with system.
alien wrote:Demos often use all of RAM. TOS expects part of that RAM to contain its variables. Therefore TOS isn't any use. Also TOS runs its own interrupts that take up too much CPU or occur at inopportune times.
Instead of using TOS, demos often use custom floppy loaders. It's not an OS, just a barebones floppy disk driver that loads the demo to RAM, unpacks it, and runs it. To run this type of demo from a harddrive, a custom driver is often needed to access the harddrive.
Mikefulton wrote:None of this is news, but my experience is that there's often a big gap between what's actually necessary to produce a desired result, and what people THINK is necessary.
alien wrote:Mikefulton wrote:None of this is news, but my experience is that there's often a big gap between what's actually necessary to produce a desired result, and what people THINK is necessary.
I'm sorry, I thought you were genuinely interested. I'm quite confident Leonard can code.
-HDD low level sector loading ( how to load sector #n without using driver or TOS )
-HDD FAT handling ( I have to know the exact sector list of the two MSA files on the HDD)
Anyone have info regarding that stuff?
fenarinarsa wrote:Pardon my ignorance, but as far as I know by reading various documentations, if you do a low-level access to an HDD you need to support both the filesystem and the HW protocol used by the HDD.
Granted ACSI & FAT16/FAT32 is the most used on ST and I guess you can code your own driver for that, but you may hit a wall when your demo run from a non-standard mass storage device or FS. And I think now most ST users use some kind of HDD emulator based on SD card/network/emulated FS, and you also need to take into account that your demo may run from a floppy disk (high-capacity extended floppy formats are available through HW emulators like HxC).
So maybe you should consider using GEMDOS calls after all
Users browsing this forum: No registered users and 11 guests