home *** CD-ROM | disk | FTP | other *** search
Wrap
From: David.Norman@ttlg.UUCP (David Norman) Sender: postmaster@ttlg.UUCP Path: sparky!uunet!wupost!gumby!destroyer!ubc-cs!unixg.ubc.ca!kakwa.ucs.ualberta.ca!alberta!ttlg!postmaster Newsgroups: comp.sys.ibm.pc.hardware Subject: DTK 486 with Symphony chipset - relocating shadow ram Message-ID: <715852838.1@ttlg.ttlg.UUCP> Date: 06 Sep 92 23:22:22 mst Lines: 32 Hello Duncan! 02 Sep 92 16:27, Duncan Murdoch wrote to All: DM> From: dmurdoch@mast.queensu.ca (Duncan Murdoch) DM> nsu.ca!mast.queensu.ca!dmurdoch Newsgroups: comp.sys.ibm.pc.hardware DM> Subject: DTK 486 with Symphony chipset - relocating shadow DM> ram Organization: Queen's University DM> @Message-ID: <dmurdoch.108.715451222@mast.queensu.ca> DM> Date: Wed, 2 Sep 1992 16:27:02 GMT DM> DM> I've got a DTK 486-33, with DTK's own BIOS, and a Symphony chipset. One DM> of the config options is a choice between relocating 0K and 256K of DM> the shadow ram. The manual is quite vague about what this does, but with DM> 0K relocated, I have 384K of memory dedicated to shadow ram, and with 256K DM> relocated, only 128K of memory is used that way. DM> DM> The trouble is, the 256K relocation seems to confuse QEMM386 2.42. I get DM> weird crashes as though it thinks my memory is quite different than it DM> really is. If I ask for 0K relocation, the problems go away - but so does DM> 256K of memory. DM> DM> Does anyone know exactly what this relocation does, and how to tell QEMM DM> to live with it? Duncan Murdoch dmurdoch@mast.queensu.ca -+- Fred-Uf 1.8k DM> + Origin: Passed through TTLG: UUCP <> ProgNet gateway (42:1000/2.0) Dtk Uses strange ways to do things. You can tell qemm not to shadow roms with the noshadow command. Or you can change the bios to a real one. The chipset os ok, but the bios stinks. David * Origin: Dave's Place - Edmonton Alberta (42:100/37)