The process to make a Kickstart 3.9 ROM set is as follows:
Amiga os 3.9 usb 3 Pc#
Amiga os 3.9 usb 3 driver#
For example you could remove the original vice from the ROM image if you don't use the Amiga's original on-board IDE interface, and instead add a different device driver needed for the HD hardware you actually use, such as vice.
Amiga os 3.9 usb 3 Patch#
Therefore allowing the Amiga to boot into AmigaOS 3.9 without first needed to patch the system and perform a soft reboot.Īnd while creating this custom ROM image you can take the opportunity to customised the files it contains for your own needs. And a new ROM is then built which contains both. The custom 3.9 ROM is built by combining the files from the original Kickstart 3.1 ROM version, with the files from the AmigaOS 3.9 ROM update. By combining the files from the original Kickstart 3.1 ROM with those included in the AmigaOS 3.9's ROM Updates and making a new updated ROM it removes the Amiga's need to first need to run the setpatch to add the newer files into the system. This is where this custom Kickstart 3.9 ROM comes in. Logically, had Commodore still existed they probably would have released an updated kickstart ROM that contained the updates this Patch adds, instead of needed to patch the system in memory every time it boots. Kickstart 3.9 is instead is a custom "scene/homebrew" ROM created by the Amiga community for use with AmigaOS3.9.Īlthough AmigaOS 3.9 boots fine using a Kickstart 3.1 ROM, before AmigaOS 3.9 actually loads it normally first needs to patch the system by running setpatch to add the additional AmigaOS ROM Updates required for 3.9, and then once they are loaded/patched the system reboots and then loads AmigaOS 3.9. Press the CTRL key during the startup to get it forced to the VESA mode, or press the Shift key or LMB to get into the early startup boot menu where you can select between some other modes.There wasn't an official Kickstart 3.9 ROM released by Commodore, or any other Amiga company. These are probably created only after user has manually saved some related settings.Īnd of course you could try to boot MorphOS into some default resolution instead to a saved one. I think that if these files are missing, MorphOS tries to use something that it finds for defaults and it should work as booted from the installation media. And if this doesn't help, try the same with the System:Prefs/Env-Archive/sys/PublicScreens.prefs file. This defines which resolution and monitor Ambient and other screens are trying to open.
You could remove (or rename to different name to be revertable) the System:Prefs/Env-Archive/MUI/screens.txt file. Withouth thinking this too well now, I'd have couple quick suggestions. It's good that it works when booted from the USB stick, then you can get it to work from the installed system too. But also if I enter there the correct values of my monitor, save and then try to boot with the SSD disk, I get the 'wrong screen resolution' message. The only strange issue: In prefs/monitors a wrong monitor (31kHZ) is set. Yes, I could boot with the help of the USB-Stick.īecause: In Prefs/Screens the correct graphics card is set (X1650Pro).ĭo I have to copy this prefs? Is this X1650 configuration only saved for/on the USB-Stick? As you can see I assume the former, but even if assuming the latter, MorphOS support would be limited to Evergreen, not Northern Islands. Even higher-numbered cards such as HD8000 family up to HD8490, and Rx 200 family up to R5 235 have supported TeraScale 2 GPU.ītw, there's some ambiguity whether the names "Evergreen", "Northern Islands", "Southern Islands", "Sea Islands", "Volcanic Islands", "Caribbean Islands" and "Arctic Islands" denote graphics cards families (HD5000, HD6000, HD7000, HD8000, Rx 200, RX 300 and RX 400/500) or GPU microarchitecture generations (TeraScale 2, TeraScale 3, GCN1, GCN2, GCN3 and GCN4/Polaris). Likewise, the Southern Islands (HD7000) family of cards also contains such with TeraScale 2 GPU (HD7670 and below), which are supported by MorphOS. The Northern Islands (HD6000) family of cards also contains such with TeraScale 3 GPU (HD69x0) that isn't really supported by MorphOS. It's more complicated than that because the actual GPU microarchitecture line doesn't run along the graphics card family line. we are limited to northern island and lower cards.