Path: utzoo!utgpu!watmath!iuvax!rutgers!sunybcs!bowen From: bowen@cs.Buffalo.EDU (Devon E Bowen) Newsgroups: comp.sys.cbm Subject: memory management Message-ID: <9313@cs.Buffalo.EDU> Date: 15 Aug 89 05:42:15 GMT Reply-To: bowen@cs.Buffalo.EDU (Devon E Bowen) Organization: SUNY/Buffalo Computer Science Lines: 31 I'm having some trouble shutting down the kernel area for the project I am working on. I was hoping someone had experience in this area and could help me out. I'm using a 128 in 64 mode. I'm working under C Power which seems to shut down the BASIC ROM for extra program space, but it leaves the I/O section and the kernal ROM. I need some extra buffer space for my code and I don't need any of the kernal functions, so I want to shut down that ROM area. I grab byte $01, and it with $fd (to clear the kernel ROM bit) and put it back. Now before I do this, I set up the system hardware vectors at the top and I can tell that they work great with the new vectors, so I know the ROM is getting shut off. The problem is that the program hangs in one of my functions that writes to the 80 column chip. This function has been fully tested and I know it's not a bug in the function. Now what I *think* is happening is that when I shut off the kernel ROM, I'm also somehow shutting off the I/O area! This would make the 80 column chip invisible and the function would hang. Now I don't know how this could happen since all I touched was the kernel ROM bit in that byte. Maybe an undocumented feature? Or a documented feature I missed in my reading? Maybe having both the BASIC ROM and kernal ROMs shut off automatically shuts off the I/O area? Can I get it back (I would even be will to short out some leads on the expansion bus if need be)? Any help would be *greatly* appreciated... Devon Bowen (KA2NRC) FAX: (716) 636-3464 University at Buffalo BITNET: bowen@sunybcs.BITNET Internet: bowen@cs.Buffalo.EDU UUCP: ...!{watmath,boulder,decvax,rutgers}!sunybcs!bowen