Amiga Forever by Cloanto

The purpose of this article is to document some parts of the pre-configured Amiga systems in Amiga Forever. Probably the most of the details given here can also be found in the documentation at amigaforever.com

Default folder and file locations

Kickstart and other ROMs:
C:\Users\Public\Documents\Amiga Files\Shared\rom

“Built-in Boot” when set to any of the floppy disk images:
C:\Users\Public\Documents\Amiga Files\Shared\adf

“Built-in Boot” when set to any of the hard disk images:
C:\Users\Public\Documents\Amiga Files\Shared\hdf

“Built-in Shared” when set to “Local folder”:
C:\Users\Public\Documents\Amiga Files\Shared\Workbench

When listed as “Shared\dir\something”:
C:\Users\Public\Documents\Amiga Files\Shared\dir

Pre-configured Amiga systems

Amiga 1000

Model: Amiga 1000
ROM: Amiga 1.1 (NTSC)
CPU: 68000
RAM: 256k CHIP
Media: Built-in Boot: Workbench 1.0 (floppy disk image)

Amiga 2000

Model: Amiga 2000
ROM: Amiga 1.3
CPU: 68000
RAM: 512k CHIP + 512k SLOW
Media: Built-in Boot: Workbench 1.34 (floppy disk image)

Amiga 500

Model: Amiga 500
ROM: Amiga 1.2
CPU: 68000
RAM: 512k CHIP
Media: Built-in Boot: Workbench 1.34 (floppy disk image)

Amiga 3000

Model: Amiga 3000
ROM: Amiga 3.1
CPU: 68030, 68882
RAM: 1MB CHIP + 1MB FAST
Media: Built-in Boot: Workbench 3.11 (hard disk image)

Amiga 500 Plus

Model: Amiga 500 Plus
ROM: Amiga 2.04
CPU: 68000
RAM: 1MB CHIP
Media: Built-in Boot: Workbench 2.04 (floppy disk image)

CDTV

Model: CDTV
ROM: Amiga 1.3
CPU: 68000
RAM: 1MB CHIP
Media: None

Amiga 1200

Model: Amiga 1200
ROM: Amiga 3.1
CPU: 68EC020
RAM: 2MB CHIP
Media: Built-in Boot: Workbench 3.1 (floppy disk image)

Amiga 4000

Model: Amiga 4000
ROM: Amiga 3.1
CPU: 68040
RAM: 2MB CHIP + 4MB FAST
Media: Built-in Boot: Workbench 3.11 (hard disk image)

Amiga 600

Model: Amiga 600
ROM: Amiga 2.05
CPU: 68000
RAM: 1MB CHIP
Media: Built-in Boot: Workbench 2.04 (Floppy disk image)

Amiga CD32

Model: CD32
ROM: Amiga 3.1
CPU: 68EC020
RAM: 2MB CHIP
Media: None

Walker Prototype

Model: Walker
ROM: Amiga 3.2 (beta)
CPU: 68030, 68882
RAM: 2MB CHIP, 4MB FAST
Media: Shared\dir: Walker-System
Media: Shared\dir: Walker-Work

Amiga 4000 PPC

Model: Amiga 4000
ROM: Amiga 3.1
CPU: 68040
RAM: 2MB CHIP + 256MB Z3 + 128MB PPC
PPC: CyberStorm (exclusive mode)
SCSI: CyberStorm PPC
Video: RTG (Picasso IV)
Media: Built-in Shared: Local folder
Media: Deploy a-750mb.hdf

Workbench 1.3

Model: Amiga 2000
ROM: Amiga 1.3
CPU: 68000
RAM: 512k CHIP + 2MB FAST + 512k SLOW
Media: Built-in Boot: Workbench 1.35 (hard disk image)
Media: Built-in Shared: Local folder

Workbench 3.x

Model: Amiga 4XXX
ROM: Amiga 3.X
CPU: 68020, 68882
RAM: 2MB CHIP + 64MB Z3
Video: RTG (synthetic), 16MB
Media: Built-in Boot: Workbench 3.X (shared directory)
Media: Built-in Shared: Local folder
Media: Shared\dir: Work

AmigaSYS

Model: Amiga 4XXX
ROM: Amiga 3.X
CPU: 68020, 68882
RAM: 2MB CHIP + 64MB Z3
Video: RTG (synthetic), 16MB
Media: Shared\hdf AmigaSYS4.hdf
Media: Shared\dir AmigaSYS4-Work
Media: Shared\dir

AROS

Model: AROS
ROM: AROS Latest
CPU: 68020, 68882
RAM: 2MB CHIP, 64MB Z3
Video: RTG (synthetic), 16MB
Media: Shared\dir AROS

Some resources:

ROM and Operating System Files in Amiga Forever
Classic Support Media
Amiga Forever 3.X ROM Improvements
Amiga Forever Workbench 3.1 Improvements
Amiga Forever Workbench 3.1 Duplication Instructions
Amiga Model-Specific ROM Differences

Burning Kickstart ROMs for the Amiga

(cloned from https://www.software-by-mabe.com/blog?3&catid=2)
Links and inline-notes, both displayed in red, has been added to this guide after cloning.
See also:
Burn Damn ROM Burn

Burning your own Amiga ROMs (EPROMs)

01/26/2019 | Amiga | Amiga ROM AmigaOS

With the release of the latest AmigaOS version (3.1.4) the package you could buy included ROM images to be used for either maprom (depending on your accelerator card tool support) or for burning it to a ROM.

Maprom is probably preferred, because it’s more flexible, but not always possible. For instance the A3440 card can’t do maprom. Or if you have no accelerator at all you can’t do maprom either.

Which leaves only a few options. Either you can buy the ROM, have someone burn it or burn it yourself.

Here I want to show how it works to burn it yourself.

What you need:

– an EPROM programmer. I have chosen the low cost GQ-4×4 USB programmer.

– to program the EPROMs used in an Amiga you have to get a 16-Bit 40/42 pin ZIF adapter board for the burner:
ADP-054 16 Bit EPROM 40/42 pin ZIF adapter

– an UV eraser, which can erase the EPROMs, in case something goes wrong.

– then you need EPROMs. The types used in A500/A600/A2000 are 27C400. I found the following to work which can be ordered in eBay: AMD27C400

– for burning ROMs for A1200/A4000 you need 27C800 / AMD27C800 roms, two of them to burn one ROM.

– and certainly a ROM image you want to burn.

Sometimes there are good offers at Amazon or eBay for a complete package (except the EPROMs).
You shouldn’t pay more than €150 for the GQ-4×4, the adapter board and the eraser.
(https://www.amazon.co.uk/gp/product/B011HVON3A/)

Here is a picture of the device with attached adapter board with an EPROM inside.
GQ programmer with adapter board and EPROM

Then you need to download the software for the burner. That is a) the burner software itself named “GQUSBprg”. The latest version as of this writing is 7.21.
And you need the USB driver 3.0.

Can be downloaded here: http://mcumall.com/store/device.html

When you connected the burner and installed the software we can start.
Now open the burner software. Make sure that there is no EPROM put in.

1. first step is to select the device, or the EPROM to burn.

Make sure you choose either AM27C400 or 27C400.

2. Next we’ll make a voltage check to see if the burner has all voltages in order to properly burn the EPROM.

I found that while you can attached a power supply on the burner it is not required. The USB provides enough power.

3. Load the ROM image into the buffer.

When you load the image make sure you choose .bin (binary).

!!! This is important, or otherwise the programmed ROM won’t work.
After you loaded the ROM image, you have to make sure to swap bytes.
This can be done in the ‘Command’ menu of the software.
Check first by selecting the “Buffer” tab. If you find some readable text in the beginning of the buffer, you need to byteswap it.

4. Now you have to put in your EPROM into the ZIF slot.

Make sure it sits tight and doesn’t move anymore.

5. Make a blank check to see if the EPROM is empty.

6. When the EPROM is blank we can write it.

When the write process is finished it’s done.

You can take out the EPROM and put it into the Amiga and it should work.

Some notes:
Partly this whole process of writing the ROM was a real pain because the GQ burner would just stop writing at some address. And in fact I had to get the package replaced including the adapter board.

I had first tried it in a virtual machine (VMware Fusion on Mac) but this doesn’t work for some reason as the GQ programmer detaches and re-attaches to the USB bus on some of the operations and that doesn’t seem to be working reliably in a VM.

Commenting on my own post:

The Amiga 4000 can only use 512k EPROMs, hence only 27C400 will work.
The Amiga 1200 can also use 27C800 (1MB).

The byte-swap, if your ROM image is already byte-swapped, then you don’t need to do this here.
Some ROM images, which are ready to burn have this already.
However, if you want to burn ROM images that are used in maprom or UAE, then you have to byte-swap.

07/15/2019 | Manfred |


Resources

Making a custom kickstart 3.9 ROM
Guide: Create and Burn a custom Kickstart 3.9
AmigaOS 3.9 Kickstart and Patches Guide
Classic Amiga Wiki – Kickstart 3.9
Help making Custom Kickstart rom
EEPROM on A1200?
Making a custom kickstart 3.1.4 ROM
Remus and ROMsplit to create your own 3.1.4 KS


Willem EPROM programmer
GQ-4X User’s Manual
Software and USB-driver download
27C400 EPROMs (for A500/A600/A2000 and A4000 ?)
27C800 EPROMs (for A1200 only ?)

Cisco ASA5505

Konfiguration

Mappa extern IP-adress till intern
Port forwarding (närmast rätt)
Cisco ASA CLI/ASDM for Dummies

När saker inte fungerar

När det inte går spara konfigurationen (full flashdisk):
Om det finns någon gammal version av ASA eller ASDM, så går den plocka bort med “delete”-kommandot
show disk
delete disk0:/asa-gammal-fil.bin

Byta version på adsm eller asa som laddas:
enable
conf t
asdm image disk0:/asdm-792-152.bin
boot system disk0:/asa924-33-k8.bin
write memory
reload

Laga trasig ASDM-inloggning
https://www.grandmetric.com/knowledge-base/design_and_configure/cisco-asa-enable-asdm-access-asa/
To enable ASDM on Cisco ASA, the HTTPS server needs to be enabled, and allow HTTPS connections to the ASA.
To configure ASDM (HTTP) access to Cisco ASA on particular interfaces, where core and management are the nameifs use following commands:

ASA(config)#aaa authentication http console LOCAL
ASA(config)#http server enable
ASA(config)#http 0.0.0.0 0.0.0.0 inside

Remember to create username, password to be able to authenticate to asdm:

ASA(config)#username admin password secretpassword

Uppdateringar

(låst) ASDM och ASA

http://download.escope.net/cisco/

http://www.celinacomputers.com/

Cisco ASDM
Cisco ASDM 7.12.2
Cisco Software Download – ASDM bra att kolla vilken version som ska letas

Cisco ASA 9.12.2
Cisco Software Download – ASA 5505 – kolla version här

Video Tutorials

Cisco ASA 5500 Password Reset Recovery

Cisco 5505 Factory Restore

Cisco ASA Training 101: ASA 5505 Firewall Initial Setup

Cisco ASA5505 firewall teardown an detailed overview for CCNA security lab and repair