The SSD driver I'm using uses memory at $200 ish for its timer routines but it also uses some memory around $1500 - $2200 ish for something which I presume is the bit causing the problem. In case its of any help I'm using several GEMDOS routines for reading directories (setdrv, chdir, sfirst & snext) and loading files (set DTA, sfirst, open, read and close).Grazey wrote:Quite a few music routines use memory around $200 (SSD , Lotus etc)
Nice one, I'll be sure to rip out that replay routine for my player. At this rate my credits screen will say Grazey about 10 times and a few mentions of other people that have kindly shared their wisdom.Grazey wrote:Regarding Ghostbattle, my latest SNDH of GB removes all Word addressing so the tune can be played from any address
Code: Select all
Pink/RG wrote:Adding this routine onto my VBL fixed everything:
gwEm wrote:i guess you looked at the SSD replay rout sources available on dhs.nu?
Pink/RG wrote:I believe some hard disk drivers use the 200hz system counter ($4ba) that timer c drives.
ijor wrote:TOS doesn't use the 200hz timer for any disk code anyway. Yes, as said, a third party hard disk driver might. It might use it for timeouts and for write back cache flushing.
Grazey wrote:Regarding Ghostbattle, my latest SNDH og GB removes all Word addressing so the tune can be played from any address. OCWAS ULM, OCWAS Mainmenu, also use this driver.
unseenmenace wrote:ijor wrote:TOS doesn't use the 200hz timer for any disk code anyway. Yes, as said, a third party hard disk driver might. It might use it for timeouts and for write back cache flushing.
Anyone know if that would include STeem's virtual hard drives?
unseenmenace wrote:It took me a while to figure out that OCWAS was "Oh Crikey What A Scorcher" lol. Incidentally is it OK to "borrow" your modified Ghost Battle routine? It'd save me some grief
Users browsing this forum: No registered users and 2 guests