in normal startup-sequence, try to disable ShowAmiga96, so you can see what is happening behind the picture during the boot process. Like it is written in website, IPrefs might crash sometimes. In that case, try to increase the value of WAIT commands before and after the IPrefs in startup-sequence. (eg. C:Wait 3)

thanks for your advice, will try these things out
I'm kinda against emulators since my religion is using real Amiga's but this package and others lika AmigaSys is really cool and I might use some bits of it on my real Amiga's, hope to see AmiKit also for real Amiga's

I downloaded & installed the AMIKIT programme including the adding my own CD 3.9 version & both boing bags in under 20 minutes.
The only "wierd" bit was allthough the OS3.9 installed from the 1st PC cd device , I had to swop it to the second device before it was recognised by AMIKIT to install the boing bags.
Since this is typed in using the Ibrowse config from the programme , I can say its handling SEEMS exactly the same as my own 1200 setup.
However I have yet to stretch it with any real application yet
So I will be resrving judgement till then

The only "wierd" bit was allthough the OS3.9 installed from the 1st PC cd device , I had to swop it to the second device before it was recognised by AMIKIT to install the boing bags.

i noticed the same, only the CD0 driver is installed, amikit chooses my LG DVD burner and not my Toshiba DVD drive as the first drive. You need to install also the cachecdfs driver for CD1 and CD2 (the daemon-tools drive).

i noticed the same, only the CD0 driver is installed, amikit chooses my LG DVD burner and not my Toshiba DVD drive as the first drive. You need to install also the cachecdfs driver for CD1 and CD2 (the daemon-tools drive).

If you want to enable the support for more than one CD/DVD drive, simply move the CD1 (CD2, CD3, CD4) file from AmiKit:Storage/DosDrivers/ to AmiKit: Devs/DosDrivers/. For temporary activation of these drives simply click the boingball located on the taskbar -> Utilities -> System -> DOS Drivers -> and choose the drive you want to activate.

PS: I was afraid of getting "CD1 not found" message during the startup, that's why CD0 is installed only...

Quote:

Originally Posted by Retro-Nerd

btw: I've noticed that the thumbnails from OS3.5 & png icons are not shown correctly in the icon information screen.

nice Workbench-only setup Retro-Nerd! Since you're not using DOpus, put RAWBInfo back to WBStartup. You should find it in AmiKit:WBStartup/Disabled.

I had to name my C: drive. Doesn't matter what, but it can not be blank.

Basically there is a file called AFOnline in the \AmiKit\Prefs\Env-Archive folder which contains the location of the Amiga Forever system files (for AF2005 it is C:\Documents and Settings\All Users\Documents\Amiga Files\System...which I think is RETARDED! All program information should be saved within the program directory, not scattered about! Eh, just an old programmers state of mind I guess... /rant off)

It basically did not have a drive name, so it was confusing the install.
(:\Documents and Settings\All Users\Documents\Amiga Files\System instead of
XP:\Documents and Settings\All Users\Documents\Amiga Files\System, where XP is the name of the drive)

OK. Just in case someone else runs into this issue!
Basically there is a file called AFOnline in the \AmiKit\Prefs\Env-Archive folder which contains the location of the Amiga Forever system files (for AF2005 it is C:\Documents and Settings\All Users\Documents\Amiga Files\System...which I think is RETARDED! All program information should be saved within the program directory, not scattered about! Eh, just an old programmers state of mind I guess... /rant off)

The scattering about and hiding you most wanted stuff and displying things you don't want to see.....that's how MicroSoft believes how you want things :/

Good thing I have an ISO of Amithlon on me HD, my WB3.5 and 3.9 is in Norway still

i got some WinUAE crashes with AmiKit. XP reports a bug to the nt.dll. I'm using Xp with SP2. Any idea?

i also noticed that my coloursettings sometimes changes as shown in the screenshot, i mean the ughly yellow. After a reset all is fine again. I know this problem from other amiga packages like AIAB, mostly after changing some settings in the GUI prefs.

microgolded reports a "can't delete file Amikit:s/startup-sequence" when i want to save a changed startup-sequence. But the settings are still saved.

I had to name my C: drive. Doesn't matter what, but it can not be blank.

yes, I must confirm this bug. When you plan to install AmiKit using AF2005-Online Edition as a source of system files, please give a name to your Windows C: drive (eg. WinXP or whatever). Once the AmiKit is successfully installed, you can remove this name. I hope the fixed AmiKit.exe GUI will be ready soon...

i got some WinUAE crashes with AmiKit. XP reports a bug to the nt.dll. I'm using Xp with SP2. Any idea?

what source of system files have you used? When does the crash appear exactly? btw. maybe it's something WinUAE related and not AmiKit...

Quote:

Originally Posted by Retro-Nerd

i also noticed that my coloursettings sometimes changes as shown in the screenshot, i mean the ughly yellow. After a reset all is fine again. I know this problem from other amiga packages like AIAB, mostly after changing some settings in the GUI prefs.

generally, this is the problem of VisualPrefs and OS itself... Changing the settings on the fly is not so easy...

Quote:

Originally Posted by Retro-Nerd

microgolded reports a "can't delete file Amikit:s/startup-sequence" when i want to save a changed startup-sequence. But the settings are still saved.

yes, it happens to me as well. This is due to NTFS partition where your AmiKit is installed. This message doesn't appear under FAT32 or .hdf
Again, this behaviour is related to WinUAE and its amiga disk emulation and/or Windows NTFS...

what source of system files have you used? When does the crash appear exactly? btw. maybe it's something WinUAE related and not AmiKit...

generally, this is the problem of VisualPrefs and OS itself... Changing the settings on the fly is not so easy...

yes, it happens to me as well. This is due to NTFS partition where your AmiKit is installed. This message doesn't appear under FAT32 or .hdf
Again, this behaviour is related to WinUAE and its amiga disk emulation and/or Windows NTFS...

The crashes are randomly, most when i try to change & save settings. Or when i copy files with DirOpus 4. But it maybe crashed in other actions, i can't remember. I will try to copy my Amikit package to a .hdf, maybe it works more stable. Thanks for the hints.