| - S0rin (QUIT: Ping timeout: 265 seconds) (~S0rin@user/s0rin) | 01:25 | |
| + S0rin (~S0rin@user/s0rin) | 01:27 | |
| + gdonner (~gdonner@c-98-253-93-116.hsd1.in.comcast.net) | 06:42 | |
| gdonner | @Jope: By any chance do you know of a modern (or at least reliable) "MapROM"-like utility that can boot AmigaOS directly from a DEVS:Kickstart file? | 06:43 |
|---|---|---|
| gdonner | Jope: Just something that's friendly to the ZZ9000 and my newly-installed BFG9060. :) I do miss C='s "MapROM" tool; super lean, easy to use, and worked perfectly. | 06:44 |
| - gdonner (QUIT: ) (~gdonner@c-98-253-93-116.hsd1.in.comcast.net) | 06:52 | |
| apolkosnik[m] | MuMapROM? | 06:57 |
| norly | What apolkosnik[m] said - MuMapROM works great! | 10:04 |
| norly | https://aminet.net/package/util/libs/MMULib | 10:04 |
| + gdonner (gdonner@c-98-253-93-116.hsd1.in.comcast.net) | 15:46 | |
| gdonner | apolkosnik[m]/norly: So "MuMapROM DEVS:Kickstart"? | 15:47 |
| gdonner | I thought I checked MuMapROM's docs for 'whole Kickstart' booting and didn't see anything? Time to re-read them..! | 15:48 |
| gdonner | I was under the impression it could only copy the physical ROM chip to Fast RAM (and write-protect it). | 15:49 |
| gdonner | Argh; nvm! I'm thinking/looking at the wrong utility (MuFastRom). *argh* Sorry! | 15:51 |
| gdonner | Yes, of course--MuMapROM! Thanks! | 15:51 |
| gdonner | The only caveat with MuMapROM appears to be that it's not tailored for the BFG's RAM (not sure); i.e. "If there is any other way to install an alternative ROM, for | 16:03 |
| gdonner | example by a CPU-board specific program, you will most likely want to use this alternative program." | 16:03 |
| gdonner | I'll ask Henrick Richter if he's considered making a BFG9060-specific Kickstart boot utility that uses the BFG's RAM, instead of motherboard RAM. | 16:05 |
| norly | oh, I guess I mixed up MuFastROM and MyMapROM. I'm using MuFastROM, not MuMapROM, oops... anyway, that one does work great :) | 16:27 |
| gdonner | I was mixing them up as well--it's too easy to assume that MuFastROM does both functions, but that's not the case. :) | 16:30 |
| gdonner | I've asked on the BFG9060 a1k forum thread if it's possible to make a small utility that boots /directly/ into the BFG9060's Fast RAM, rather than slow Amiga motherboard RAM, which then would require another reboot to get into the BFG9060's Fast RAM (if I read the MuMapRom docs correctly)? | 16:32 |
| gdonner | The MuMapRom docs note that: "If there is any other way to install an alternative ROM, for example by a CPU-board specific program, you will most likely want to use this alternative program." | 16:35 |
| - gdonner (QUIT: ) (gdonner@c-98-253-93-116.hsd1.in.comcast.net) | 16:56 | |
| - WoC (QUIT: Ping timeout: 255 seconds) (woc@2603-8080-cd40-00c6-f184-fa55-2592-94cf.res6.spectrum.com) | 17:16 | |
| norly | sounds right to me, as the hardware may be built to fully transparently replace the ROM, from the CPU's point of view, while the MMU tools cannot do that. all they can do is to instruct the CPU to fool itself using its own MMU. | 17:37 |
| + WoC (woc@2603-8080-cd40-00c6-1cd4-ab60-80a6-ff7a.res6.spectrum.com) | 18:26 | |
| - WoC (QUIT: Remote host closed the connection) (woc@2603-8080-cd40-00c6-1cd4-ab60-80a6-ff7a.res6.spectrum.com) | 19:31 | |
| + WoC (woc@2603-8080-cd40-00c6-beef-beef-beef-beef.res6.spectrum.com) | 19:33 | |
| - WoC (QUIT: Remote host closed the connection) (woc@2603-8080-cd40-00c6-beef-beef-beef-beef.res6.spectrum.com) | 19:45 | |
| + WoC (woc@2603-8080-cd40-00c6-f184-fa55-2592-94cf.res6.spectrum.com) | 19:45 | |
| - WoC` (QUIT: Read error: Connection reset by peer) (WoC@2603-8080-cd40-00c6-6497-aa09-4e68-01e9.res6.spectrum.com) | 22:51 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!