Amiga.org
Amiga computer related discussion => Amiga Tutorials => Topic started by: NovaCoder on November 26, 2009, 11:11:06 AM
-
After running OS3.9 on my A1200 with its default 020 @ 14 MHz and 8Mb RAM, I was expecting a big things with my new Blizzard 030 @ 50 MHz + FPU and 64Mb RAM. Unfortunately I found that my faster processor and extra memory didn’t make that much difference to WB performance.
Most people will say if you want a fast WB with AGA then the best thing to do is run OS3.1 in about 16 colours whereas I wanted to run the latest Classic OS and I wanted it to look as modern as possible on my hardware.
This is a screen grab of my current desktop as an example.
(http://home.iprimus.com.au/novacoder/amiga_background4.jpg)
The first thing to do is settle on a screen-mode, I went for Multisync + VGA only @ 640x480 because this gives a progressive 4x3 display with a decent refresh rate and looks lovely on my flatscreen 19” CRT :)
Making it Fast
Obviously you need to install BB1, BB2 and BB3 (http:// http://eab.abime.net/showthread.php?t=36971)
These are the patches that I’ve found create a nice stable 3.9 setup which is still usable in the full 256 colour mode (obviously it will always run faster with less colours). The basic idea is to offload as much of the work as possible from AGA to your accelerator’s CPU and also to keep data transfer to a minimum across the slow interface. Generally speaking, the more patches you apply the less stable your system could become so I try to keep them to a minimum.
• BlizKick (http:// http://aminet.net/package/util/boot/BlizKick) – This awesome utility not only allows you to move the OS from your ROM to your RAM, it also includes some handy speed-up modules.
• FBlit (http:// http://aminet.net/util/boot/fblit.lha) & FText (http:// http://aminet.net/util/boot/FText.lha) – These not only free-up some much needed chipram, they also offload blitting to your accelerator.
• BlazeWCP (http:// http://aminet.net/package/util/boot/Blazewcp ) – Very fast CP2 OS replacement functions.
• IconBeFast (http:// http://aminet.net/util/boot/IconBeFast.lha) – Greatly speeds up ICON drawing in esp. in 256 colour modes.
• WBCtrl - Allows you to copy your icons to FASTRAM (used in conjunction with WorkBench Perfs, Icons to FASTRAM setting).
Also remove the AmiDock from your WBStartup draw and stick it somewhere else (eg the recycle bin).
And finally, I’d recommend a move to SFS/PFS from the standard FFS which smells bad and has been known to talk to itself on occasion.
Making it look Pretty
The default GlowIcons are nice and a big step up from OS3.1 but they are still using a limited colour palette, I decided to upgrade mine to something a bit more modern. It’s very easy to replace your Icons in 3.9; it’s a simple drag and drop while viewing the Icon’s information window.
The default WB color remapping logic can result in your icons rendered in some odd colours and your background image will often change each time you open a new window….not pretty. To fix this, we use FullPalette to create a palette matched to our main icon set and then use it to lock a subset of these colours for use by WB. We also map our background image to the same palette to avoid any colour cycling; I’ve found the best thing to do is limit the background image to as few colours as possible.
VisualPrefs is an amazing utility which allows you to greatly customise WB and generally tart it up; we also use it to remap WB colours to our fixed palette entries.
MagicMenu is another great WB utility which is not only very handy but also makes the OS feel more modern to use. You should also map the colours used by your Menus to your fixed palette entries to prevent any bizarre colour remapping….pink menus, no thanks!
BarClock although LimpidClock is more popular, I prefer the less intrusive BarClock for my setup.
I’ve uploaded a MOVIE (http://www.youtube.com/watch?v=VETGfJ9pjI0) to YouTube so you can see it in action, obviously if you’re lucky enough to have a 040/060 it will be even faster.
I will also add my setup resources to AmiNet when I get the chance (palette, Icon set, VisualPrefs settings, background images etc).
UPDATE: I've since changed to an IndivisionAGA powered HighGFX 1024x768 in 64 colours, very nice ;)
(http://home.iprimus.com.au/novacoder/laytex.jpg)
NovaCoder
-
What we need next is a really detailed tutorial on how to create SFS partitions!
-
Great tutorial!
Personally I was away from the Amiga around 1994 and missed out on everything post 3.1, this helps getting my recently acquired A4000 back into shape!
One thing that keeps puzzeling me, how do I update the complete icon set? I downloaded AB-GlowIcons from aminet, which contains a zillion icons. I don't feel like changing icons one at a time...
Any change you could update the tutorial with a hint on how you made your workbench look that great, step by step?
-
I have to admit this is one of those tutorials that's far more useful than it looks. Many Amiga returnees pulling an A1200 out of the attic will be thinking of getting just this sort of setup going. Nice work.
-
Nice!! I really like your presentation video (including the AW bugger :) ).
Btw. how do you play DOTT? Has it been ported to Amiga natively or is there some Scummvm magic at works in the background?
-
nice tutorial Nova! half the fun is setting up our Miggy's :-)
-
Yes, thanks for this guide. I wish it were not in the forum format though. Think it could be better done as a blog or a series of blogs?. My 1024x768 screen is great but soo slow. I might need to give up some resolution to make WB work better, I like 64 colors.
EDIT - just watched the video - very cool. But you know, that 256 color is still dragging on 640x480. Do you have some cache setting running for your boot partition?
C: AddBuffers >NIL: DH0: 250
Helps a little when re-loading, or re-visiting windows.
How did you do the video, NovaCoder ? Looks good.
-
Thank you for your good tutorial!
PS:Have you tryed systempatch 3.3? It does a ton of speed up patches on AGA, and already includes iconbefast and blazewcp. Besides it is fblit and ftext compatible! http://www.ziosante.it/it/articoli-e-downloads/amiga/70-systempatch-33beta-sources-download
-
@NovaCoder
Very impressive and great job! It's nice to see this instead of just another "use OS 3.1 post" when asking about how to speed up 3.9.
Questions:
* Looks like your bootup time is considerably faster than my 1200's CF card. I was wondering if you could post your startup-sequence so I could compare.
* I have the B1260 card as well and I am not using blizkick because I thought the card does this ROM->RAM mapping automatically if the jumper is set. A little confused on this.
-- edit: I wish we had a central site or main FAQ that this kind of great info. One of the most frustrating things for returning Amiga users (like myself) is trying to find info on the net. My knowledge had stopped at ks2.0 and this has been the biggest hurtle for me.
So many really old FAQs that have dead links or outdated information.
-
OMG!
Thank you for informative stuff. Have been with Amiga (A500plus/A2000)since 1992, I just bought my first A1200 (still coming from UK:) and also bought Indivision AGA card, so I might just get somewhere with this, thanks to you too! I'm thinking some 040/060 card would be much "modern" in terms of usability of multicolor WB...
-
* I have the B1260 card as well and I am not using blizkick because I thought the card does this ROM->RAM mapping automatically if the jumper is set. A little confused on this.
Moto, if you see flashing colours on your screen when you first turn on your amiga, then your kickstart is mapped to RAM. :)
Blizkick is used for mapping an actual kickstart file into ram....for example, users with 3.0 ROMS can softboot 3.1 if they wish by using Blizkick.
-
-- edit: I wish we had a central site or main FAQ that this kind of great info. One of the most frustrating things for returning Amiga users (like myself) is trying to find info on the net. My knowledge had stopped at ks2.0 and this has been the biggest hurtle for me.
So many really old FAQs that have dead links or outdated information.
Maybe we could setup a Wiki on amiga.org with a FAQ style setup? Have a button in the top menu, voila!
-
Nice!! I really like your presentation video (including the AW bugger :) ).
Btw. how do you play DOTT? Has it been ported to Amiga natively or is there some Scummvm magic at works in the background?
Ahh, I'm sooo happy now that it (Day of the Tentacle) can be played on AMIGA!!!
http://amiga.h-plus-t.com/
btw sorry NovaCoder for offtopic...
-
Oh, I see, veeery nice indeed :)
So, now what about Sam & Max? :D
Sorry for continuing OT...
-
Ahh, I'm sooo happy now that it (Day of the Tentacle) can be played on AMIGA!!!
http://amiga.h-plus-t.com/
btw sorry NovaCoder for offtopic...
Maybe you should make a link to novacoders version of dott for the amiga: http://www.underground-arcade.com/Downloads.php
I think he will get offended since this is his thread :)
-
Oh, I see, veeery nice indeed :)
So, now what about Sam & Max? :D
Sorry for continuing OT...
Yep Sam & Max is coming, it's what I'm working on now ;)
Anyway back on topic.....
Cool glad you guys like this little guide. I'm not an expert or anything, just wanted to give a write-up of what I've discovered so far.
Obviously WB will always run quicker with less colours but I wanted to show that you can create a 'useable' WB in 256 colours without RTG.
Yep I've heard about SystemPatch and it's another option but I prefer to choose which patches I'm applying ;)
-
PS:Have you tryed systempatch 3.3? It does a ton of speed up patches on AGA, and already includes iconbefast and blazewcp.
And FText. However, i have found that some of these patches perform a little faster than SystemPatch on 68020-68030 CPUs, according to AIBB benchmarks. Some SystemPatch routines are specially optimized for 68060, iirc, but work fine on all 020+ CPUs.
Yep I've heard about SystemPatch and it's another option but I prefer to choose which patches I'm applying
SystemPatch gives you complete control on which patches will be installed. It's important to skip the loadseg and intuition.library patches by adding -loadseg and nointuition.
-
What resolution are you using ?
Seems very slow compared to mine ...
-
What resolution are you using ?
Seems very slow compared to mine ...
You have Indivision and dont have to run Multisync + VGA only :)
-
You have Indivision and dont have to run Multisync + VGA only :)
Oh, me being blind/rude again, sorry :o
I don't have Fblit&Ftext and Iconbefast installed, might just try them, because when running 1024x768 OS 3.9 slow's down alot.
-
I forgot...
env-handler is really good on saving precious chipram and makes booting, at least for me faster!
-
@NovaCoder
When you go into the 'looking good' patches, why no Birdie mention? I thought this was a normal staple for 68K WB? VisualPrefs can not add the backrounds to title areas or replace the window gadgets, is that correct?
-
Hiya,
Yep thats right but I didn't really get on that well with Birdie so I just used VisualPrefs to change the title bars as shown in the screen grabs.
-
I'm now running in 1024x768 @ 64 colours (icons in FASTRAM)...very nice :)
-
Screens, pleeeease!! :)
-
I'm now running in 1024x768 @ 64 colours (icons in FASTRAM)...very nice :)
Me too, got it all working good. I don't need no stinkin birdie either...
I'll send up a shot or two tonight...
-
Hey guys, I'm waiting for those screenshots! :D
-
Hiya,
I can't get the screen grabber to capture my nice 1024x768 properly :(
Anyone at the last Victorian Amiga users group meeting got a good look at it though!
:)
-
ah, what a pity :(
But it's good to know the locals could see it :D
-
trying, problems with sgrab and .png - will try some other format ...
To the new owner, whoever you are - increase our file upload sizes / demensions so we can see 1024x768 in all its glory.
-
http://aminet.net/package/util/misc/gfxroute check that, and pay attention to fscreen. That thing greatly speeds up aga. And tlsfmem of course. If you have an 040 or 060, look into copymem and some other recent patch i cant remember the name of.
-
Well I'm disappointed, I'm using sgrab (I like it) and have installed a jpeg library that it wanted. So when I makes some grabs, bring them over to the laptop, they won't display. Not even in photoshop. Photoshop complains:
"unkown or invalid jpeg marker type is found"
:( :furious:
-
Yay! had to install the boring 020 version jpeg.library to get sgrab to work. Here are the results of this thread - the Corduroy Workbench:
(http://152.2.39.53/wb1.png)
(http://152.2.39.53/oss1.png)
(http://152.2.39.53/wb2.png)
-
Very nice! Thanks a lot for your effort.
-
Okay guys and gals,
this thread and the one about work being completed on an unofficial BoingBag3 have motivated me to stop working on my current A3000 and A3000T projects and go back to my A1200/060/256mb Fast RAM & Blizzard SCSI.
I have just finished tearing it down to remove the 4gb hard drive and replace it with an 8gb Compact Flash card and IDE to CF adapter. The CF is now partitioned and formatted and I have installed AmigaOS3.9, but not the BoingBags 1 & 2 yet.
My question is, do I start at the beginning of this thread or should I install the unofficial "BoingBag 3" and then come back to this thread and install what is suggested here? Also, are there starting to be some conflicting alternative suggestions in this thread for what are the best patches and programs to install to get the best and fastest AGA Amiga setup?
Here are my complete specs for my system:
Late model A1200 - Oct 12th, 1995 stamped in ink inside the case top
Rev 1D4 Motherboard
Blizzard 1260 rev. II w/SCSI module and 256mb RAM
8gb CF card on internal IDE header via IDE-> CF adapter
IndivisionAGA 1200 connected to a 19" CRT
current display settings are 1440x400 w/64 color Workbench, but will look at 1024x768 HighGFX when I get it downloaded and installed
External Zip250 & CD-ROM connected to Blizzard SCSI module's external connector
Subway USB controller w/registered Poseidon stack & 4 USB ports (2 back & 2 side of case)
New AmigaKit floppy drive (bought at AmiWest 2009, thanks Matthew)
Wireless Network card for Miami Deluxe & IBrowse2.4
I think that is everything?
Advice on how to make this an ultimate and fast as possible AGA AmigaOS3.9 machine will be greatly appreciated.
Old-time Amiga user > then long time Amiga collector > now enjoying being an active Amiga user again.
-
I am glad that BoingBag 3 has motivated people to use more their Amigas!
All recomendations are good, the choices you make should really depend on your point of view and Amiga usage. It is allways a good policy to try out things out first, and then decide based on results you get.
By the way, you ´ve got a very nice AGA setup!
PS: Has anyone tryed CybergraphX 4.x AGA driver on a 68k? How does it perform?
-
I am glad that BoingBag 3 has motivated people to use more their Amigas!
All recomendations are good, the choices you make should really depend on your point of view and Amiga usage. It is allways a good policy to try out things out first, and then decide based on results you get.
By the way, you ´ve got a very nice AGA setup!
PS: Has anyone tryed CybergraphX 4.x AGA driver on a 68k? How does it perform?
I have the CybergraphX 4 CD here, so I can install the driver and let you know what it looks like using my IndivisionAGA if the two are compatible together.
The reason I asked my question is I, like many other returning Amiga users missed out on that period of time when most of the third party patches and improvements were being created, discussed and tested, so I have no knowledge of them except the recommendations I can get from other users who were active at that time and over the years have kept up with each new development for the Classic Amiga models and last improvements for OS3.9.
It is very easy to install something and screw up a perfectly good OS installation and it is sometimes hard to reverse such screw-ups. I had just such an occurrence this morning and I still don't know exactly what was the cause of the problem that took down my A1200. This was also a reason for me to take apart the A1200 and switch from the 4gb hard drive to the 8gb CF card as the 4gb hdd would no longer boot. I think it was the BoingBag 1 or 2 ROM updates, so I have not installed BoingBags yet until I read more in these threads. I was hoping that someone with a Blizzard 1260 and IndivisionAGA would chime in and offer to tell me what setup he/she is using and which patches, programs and utilities I should install to match their fast AGA setup. I am too tired and busy to keep using trial and error method, but that is what I will do if there is no easier way to get where I want to be.
-
I am sorry that my setup doesnt match your own, so i could help you out. But i am sure some Amiga user over here will be willing to give you a helping hand.
By the way, backups are a good habit that will save you more than half of those headaches!
Good luck!
-
I am sorry that my setup doesnt match your own, so i could help you out. But i am sure some Amiga user over here will be willing to give you a helping hand.
By the way, backups are a good habit that will save you more than half of those headaches!
Good luck!
Yeah, I am booting now from a ZIP100 optical disk, so I did have a backup. I am just anxious to get this done as quickly as possible so I can get back to a couple of other Amiga projects that are in pieces all over my kitchen table, the pool table and the game room coffee table and floor.
I was hoping when I saw the thread that someone had put everything into one neat package that I could install as easily as OS3.9 itself and just tweak a couple of settings to match my setup and be done with it. The idea of installing one component, testing, backing up and then repeating the process for the next component, when there may be 20 to 30 (or 50) different components required to be updated, added or patched is a very time consuming prospect for me.
Oh well, it will be worth it so here I go. I am going to start with a completely clean install of OS3.9 but can anyone tell me if I should, or should not check the "Install ROM updates" check box when running the BoingBag1 and BoingBag2 updates since I have a Blizzard 1260 accelerator board?
Edit: My old configuration of OS3.9 was on the hard drive when I bought this A1260 system and probably had BoingBags 1 & 2 already installed, but I installed them again to start the process of following the BoingBag3 installation instructions just in case they weren't installed. Then, when I connected a USB flashdrive to one of my USB ports on the Subway my A1200 crashed and it could not reboot, cold or warm. Something was screwed up and I was not sure what it was.
-
Okay guys and gals,
this thread and the one about work being completed on an unofficial BoingBag3 have motivated me to stop working on my current A3000 and A3000T projects and go back to my A1200/060/256mb Fast RAM & Blizzard SCSI.
I have just finished tearing it down to remove the 4gb hard drive and replace it with an 8gb Compact Flash card and IDE to CF adapter. The CF is now partitioned and formatted and I have installed AmigaOS3.9, but not the BoingBags 1 & 2 yet.
My question is, do I start at the beginning of this thread or should I install the unofficial "BoingBag 3" and then come back to this thread and install what is suggested here? Also, are there starting to be some conflicting alternative suggestions in this thread for what are the best patches and programs to install to get the best and fastest AGA Amiga setup?
Yes as I said in my original post, install BB1, 2 and 3 first (although BB3 is now 'growing').
Here are my complete specs for my system:
Late model A1200 - Oct 12th, 1995 stamped in ink inside the case top
Rev 1D4 Motherboard
Blizzard 1260 rev. II w/SCSI module and 256mb RAM
8gb CF card on internal IDE header via IDE-> CF adapter
IndivisionAGA 1200 connected to a 19" CRT
current display settings are 1440x400 w/64 color Workbench, but will look at 1024x768 HighGFX when I get it downloaded and installed
External Zip250 & CD-ROM connected to Blizzard SCSI module's external connector
Subway USB controller w/registered Poseidon stack & 4 USB ports (2 back & 2 side of case)
New AmigaKit floppy drive (bought at AmiWest 2009, thanks Matthew)
Wireless Network card for Miami Deluxe & IBrowse2.4
Nice specs, yes HighGFX 1024x768 in 64 colours should run very well on your setup.
Have you thought about ditching the IDE (blanking it off) and using an external SCSI HD?
What about a power supply for that lot?
-
I've updated my original post with my HighGFX WB now that I've got the stupid screen-graber to work ;)
-
@NovaCoder
Could you be kind enough to share that female body backdrop?
@All
Merry Christmas!!!
-
HAHAHA - Ok no fair! his workbench has much better lines than mine;
and mine was wife approved
:laugh1:
-
and mine was wife approved
That's probably the reason :D
-
Yes as I said in my original post, install BB1, 2 and 3 first (although BB3 is now 'growing').
Nice specs, yes HighGFX 1024x768 in 64 colours should run very well on your setup.
Have you thought about ditching the IDE (blanking it off) and using an external SCSI HD?
What about a power supply for that lot?
Hey NovaCoder,
I understand the instructions to install 3.9, then BoingBags 1, 2 & 3 in order, but I am still having problems. I am using an 8gb Compact Flash card in an IDE to CF adapter, connected to the A1200's IDE controller, because I wanted to reduce heat above my IndivisionAGA display enhancer. Also, the CF card is twice the size of the 4gb hdd I was using.
I have the CF card partitioned into 5 partitions. 1st one is bootable for the OS3.9 and is about .9gb in size, 2nd partition is also bootable and the same size for use as a backup boot partition and this is the one that I am doing all of my experimental BoingBag3 installs onto, the remaining 3 partitions are all about 2gb (a little less) and they are labeled Work:, Play: and Extra: for containing programs and data.
I have been very careful in my installation proceedures, but I must be missing something, some step that I have missed, because I keep coming up with the same errors, which I will list exactly below.
At the end of BoingBag3 the instructions say to alter the startup-sequence, so here is a partial listing of my startup-sequence showing exactly what I have tried. (this is at the top before anything else)
IF Exists C:IDEFix
C:IDEFix
Endif
;BEGIN BoingBag3
SYS:C/LoadModule L:FastFileSystem L:RAM-Handler L:Shell-Seg DEVS:scsi.device Libs:icon.library Libs:workbench.library NOREBOOT
SYS:C/SetPatch SKIPROMMODULES filesystem,icon,ram-handler,scsi,shell,workbench QUIET
;END BoingBag3
The original setpatch line has been removed from the script.
Then I turn off the computer and wait for 5 to 10 minutes, or on one attempt, I waited all night. Then I coldboot and get these errors.
"Loading DEVS:scsi.device failed: object not found"
"LoadModule failed returncode 10"
So, I then boot into my other boot partition and remove the "DEVS:scsi.device" part of the LoadModule line and also remove the "scsi" part of the SKIPROMMODULES line and reboot. Then I get this error.
"Loading filesystem failed: object already exists"
"LoadModule failed returncode 10"
So I then boot into my other partition again and remove the "L:FastFileSystem" part of the LoadModule line and the "filesystem" part of the SKIPROMMODULES line and reboot. I then get this error.
"ram-handler version 44 already resident"
"Loading ram-handler failed: object already exists"
"LoadModule failed returncode 10"
So, I again reboot into my other boot partition and remove ..... you get the idea. This time when I reboot, there are no error messages and I get all the way to the Workbench. I have used the "Find" feature to look for scsi.device on my system and it does not exist, but is mentioned in my "DEVS:NSDPatch.cfg", "DEVS:NSDPatch.cfg-BB3.9-1", and "DEVS:NSDPatch.cfg.BB39-2" as well as being listed in the icon files of some other DOS drivers like DEVS:Storage/DOSdrivers/CD0:, etc.
I find it hard to believe that others have not come across this same problem, since I am using the same BoingBag 1, 2 and 3 installation scripts as everyone else, but I for some reason don't have any scsi.device installed on to my system anywhere. The problem with the RAM-Handler and FastFileSystem modules not being able to be loaded by LoadModule is also puzzling.
I have not transferred my "log-files" from my Amiga to my PC, or I would attempt to attach them to this posting.
HELP!
P.S. I just unarchived IDEfix97 from my aminet CD's and took a look at it and it appears to be an old fix that has been superseded by newer fixes for TD64 being added to systems to allow >4gb devices. I wonder if I install it, if it will fail to install due to the missing scsi.device, or if it contains a version of my missing scsi.device and could fix part of my problems.
What could be more fun that working on my Amigas on Christmas Eve? (well, probably a lot of things, but I really want to figure out creating a fast and stable OS3.9 A1200/060)
Edit: @NovaCoder, I do have a 150watt PSU running my A1200 and I would not want to blank off the internal IDE and use an external SCSI hdd instead of the internal 8gb CF card. It is my understanding that the Read/Write to and from the CF should be faster and my efforts are to get the fastest stable AGA OS3.9 install that I can create.
-
@NovaCoder
Very impressive and great job! It's nice to see this instead of just another "use OS 3.1 post" when asking about how to speed up 3.9.
Questions:
* Looks like your bootup time is considerably faster than my 1200's CF card. I was wondering if you could post your startup-sequence so I could compare.
* I have the B1260 card as well and I am not using blizkick because I thought the card does this ROM->RAM mapping automatically if the jumper is set. A little confused on this.
-- edit: I wish we had a central site or main FAQ that this kind of great info. One of the most frustrating things for returning Amiga users (like myself) is trying to find info on the net. My knowledge had stopped at ks2.0 and this has been the biggest hurtle for me.
So many really old FAQs that have dead links or outdated information.
Hey Moto, looks like our A1200's are very similar in their specs. Would you be interested in sharing notes on how we are progressing with setting up fast AGA OS3.9+BB1+BB2+BB3 installations? My A1200 includes:
Blizzard 1260 w/scsi module + 256mb FastRAM
8gb CF card on IDE to CF adapter
250mb external SCSI ZIP Optical Drive (scsi unit = #5)
external SCSI Compaq CDROM drive (scsi unit = #3)
PCMCIA wireless network card from AmigaKit + EasyNET software (but I use Miami w/DHCP)
replaced floppy with new one from AmigaKit in Oct., but need to rework eject button
IndivisionAGA connected to LG 19" CRT (monitor is old and might have issues, looking for cheap LCD to replace it)
Subway USB controller w/Poseidon
Cocolino 9pin to PS2 Wheel Mouse adapter + 3 button wheel mouse
Digital to Analog Joystick adapter + Logitech Wingman
150watt PSU to run it all
-
IDEFix won't work with most CF cards, that might be your problem, check this thread (http://eab.abime.net/showthread.php?t=47196&highlight=idefix) for more details.
Also as per my original post, you would benefit from using BlizKick.
-
@AmigaDave:
I've been a little distracted with my 4000T setup recently. My 1200 came preconfigured with OS3.9 from Amigakit. Installing OS3.1 onto a CF card from scratch was a very serious endeavor for me.
My 1200: B1260 w/128mb, IDE CF-card (AmigaKit), Subway USB, Indivision AGA->Acer AL2216W, Logitech USB->PS2->Cocolino, Linksys EtherLink III, AmiTCP (same version as network boot disk). Right now I have BB1 & 2 and recently installed MagicWB (which nags me now).
I will DL the latest BB#3 and report back.
-
@amigadave
Some observations:
1. There is no point to install IDEfix and scsi.device concurrenty. Remove scsi.device from the resident modules. If the IDEFix command won't work, use LoadIDE or read the blizkick.guide on how to convert it into a resident module.
Alternatively, you can remove IDEFix and keep scsi.device.
2. Since you are using Loadmodule, why don't you just load all your modules with it? The setpatch line should become:
c:setpatch quiet noromupdate
-
If you have blizzard/cs*, you can use blizkick to load the modules, and patch for more speed, speedyide amongst others, is terribly usefull.
Also , keep an eye on the version of the scsi.device, exec and workbench.library. I had to use morelibspace REBOOT at the first line, blizkick at the second, then setpatch i believe, followed by tlsf copymem and patch060 ( latest 060/040 goodies on aminet)
-
IDEFix won't work with most CF cards, that might be your problem, check this thread (http://eab.abime.net/showthread.php?t=47196&highlight=idefix) for more details.
Also as per my original post, you would benefit from using BlizKick.
Per my post, I have not installed IDEfix, I have just located it and unarchived it to look at what it had to offer. So IDEfix can't be my problem, unless OS3.9, BoingBag1, BoingBag2, or BoingBag3 have installed it by default.
I still don't know how scsi.device is being loaded or where it is being loaded from, as I cannot locate it anywhere on my hard drive, I mean CF card.
Is it loaded from the KickstartROM? Is it created on the fly during the boot process from an archived file on the CF card? I do not know the capabilities of the AmigaDOS "Find" function to know if it can search inside of archived files too.
I don't know how to extract the scsi.device from the "resident files" to use with the LoadModule program. As I have said before, I have not installed anything other than the OS3.9, BoingBag1, BoingBag2 and BoingBag3 using the installation scripts provided with each.
So, Minuous, where am I going wrong? Does the BoingBag3 installation script only work on A3000 & A4000 computers? Is it my Blizzard 1260 card that is the problem? I am lost and don't know which step to try next.
If LoadModule is not the answer, I would need an alternative for installing patched files and moving things into FastRAM instead of ChipRAM to free up my ChipRAM and to hopefully speed up the operation of my A1200.
As always, any and all suggestions welcome.
-
Resident in the ROM, however, the Boingbag 1-2 process, updates the scsi.device, it detects what amiga you have, and updates the scsi.device thereafter ( look in the amigaos rom update file and theres a scsi.device-1200-600- 2000-3000 & 4000 & 4000T. You can use ROMSPLIT and or REMUS to _extract modules_ and build a rom, however, the shell-seq i believe, need to be pached to be put on a rom again. ROMSPLIT will allow you to extract and patch, the scsi.device patch is important. Good luck. Use http://aminet.net/disk/misc/check4gb.lha to check if your currently good on the scsi.device, there is also a patch, for the scsi.device in tlsfmem, this has been updated and its on aminet, and i believe mentioned in this post. http://aminet.net/package/driver/media/SCSI4345p anyway
-
Resident in the ROM, however, the Boingbag 1-2 process, updates the scsi.device, it detects what amiga you have, and updates the scsi.device thereafter ( look in the amigaos rom update file and theres a scsi.device-1200-600- 2000-3000 & 4000 & 4000T. You can use ROMSPLIT and or REMUS to _extract modules_ and build a rom, however, the shell-seq i believe, need to be pached to be put on a rom again. ROMSPLIT will allow you to extract and patch, the scsi.device patch is important. Good luck. Use http://aminet.net/disk/misc/check4gb.lha to check if your currently good on the scsi.device, there is also a patch, for the scsi.device in tlsfmem, this has been updated and its on aminet, and i believe mentioned in this post. http://aminet.net/package/driver/media/SCSI4345p anyway
Thanks Mike, I knew it had to be something like that, but did not know for sure what it was. So, if I understand you correctly, the AmigaOS ROM Update extracts the scsi.device and patches it then loads it into resident memory for use by the system. It appears that the BoingBag1 and BoingBag2 AmigaOS ROM Update files would do the same thing. My DEVS directory has;
AmigaOS ROM Update
AmigaOS ROM Update.old
AmigaOS ROM Update.BB39-2
The .BB39-2 file is exactly the same as the active ROM Update file, so I would imagine that the .old file is the original OS3.9 file, or the BoingBag1 ROM Update file which replaced the original OS3.9 ROM Update file. Not sure why the BoingBag2 install script would leave a second copy of the ROM Update file in the directory, but it does not matter.
My point in all of this is to point out that contrary to what I thought, after installing BoingBag3 there is still more work to be done to complete getting an up-to-date OS3.9 installation finished.
I thought that after running the recently created BoingBag3 install script I would have a finished installation that I could further enhance with some of the other suggested programs, patch files and utilities, if I wanted to, but not because I had to. At least on my system, that is clearly not the case.
I am not complaining, I appreciate all the work that has gone into the Unofficial BoingBag3. I just want it's authors to know what I have experienced so they can use the information to further improve BB3, or place notes with it that will help other users in the future.
I think I am really close to understanding what I am trying to do to get everything updated, patched and hopefully stable. I am going to attempt to build my own custom ROM file and use one of the ROM kicker programs to load it at boot time. I don't have the equipment to burn my own EPROM chips to replace the 3.1 Kickstart ROMs in my A1200.
I guess there must be legal reasons that nobody has yet started to create custom Kickstart ROM chips for various Amiga models with all the latest and greatest patched files contained in them. It would be nice if Hyperion would allow this to be done by anyone with the skills to do it, as a gift to the community. There could be competing different flavors of OS3.9 Kickstart ROMs out there to pick and choose from with different Kickstart ROM builders bragging how their ROMs are better than so-in-so's ROM chips and telling everyone why their ROM chips are the best.
It may no longer be clear who owns the rights to the Kickstart ROM chips and who can legally produce new ones, or say that new ones cannot be produced. Shame it is that way.
To everyone working on the Unofficial BoingBag3 project, please keep up the great work. This is a great service to the Amiga community and I am sure that many users will benefit from your efforts.
-
Ah, we've changed threads, I see :-)
So, Minuous, where am I going wrong? Does the BoingBag3 installation script only work on A3000 & A4000 computers? Is it my Blizzard 1260 card that is the problem? I am lost and don't know which step to try next.
It should work on any Amiga that can run OS3.9 in the first place. It should explicitly ask you what model of Amiga you use (as there has never been a reliable and supported way to determine this via the system, so best to just ask the user). Then, assuming you have selected A1200, the A1200 version of scsi.device should be copied to DEVS: (You do need to be running in either intermediate or expert mode for this to happen, though.)
But you say this isn't happening, I need to see the install_log_file to determine what's going on on your system.
I guess there must be legal reasons that nobody has yet started to create custom Kickstart ROM chips for various Amiga models with all the latest and greatest patched files contained in them.
I did this a few years ago, actually, and AmiKit decided to cause lots of dramas for everyone, getting various people's sites shut down left and right even after the Kickstart was removed. (Including, as it turns out, a medical forum, etc. ie. stuff which had nothing to do with Amiga.) He sees himself as some kind of "Cloanto representative" since he is getting paid by them to shut down sites. If you want me to send you my Kickstart 3.9, I'm happy to do so. However, BB3 is designed to work with Kickstart 3.1; some minor modifications to your startup-sequence would be necessary to use it with KS3.9.
-
>The install seems to go okay, but the two lines that are supposed to be added to the startup-sequence make it so I can't boot off that partition anymore as it stops with error messages.
Can you please send me your old S:Startup-sequence that was working for you. Which hard disk partition can't you boot from? Do you use an IDE splitter? Is your AmigaOS ROM Update the original OS3.9 one or the BB2 one? What error message are you actually getting?
>Also, can you explain to me why my system has no scsi.device after a clean OS3.9 installation?
Not really, without looking at the logfile, because it works here... :-(
You might try changing the "scsi" in the setpatch line to "scsi.device"...
-
@amigadave
type in a shell
version scsi.device full
and you will get what scsi.device is active (there's no disk-based scsi.device)
-
>The install seems to go okay, but the two lines that are supposed to be added to the startup-sequence make it so I can't boot off that partition anymore as it stops with error messages.
Can you please send me your old S:Startup-sequence that was working for you. Which hard disk partition can't you boot from? Do you use an IDE splitter? Is your AmigaOS ROM Update the original OS3.9 one or the BB2 one? What error message are you actually getting?
>Also, can you explain to me why my system has no scsi.device after a clean OS3.9 installation?
Not really, without looking at the logfile, because it works here... :-(
You might try changing the "scsi" in the setpatch line to "scsi.device"...
I have had some success getting the updated OS3.9+BB1+BB2+BB3 partition to boot by removing some of the LoadModule commands and letting SetPatch do it's thing on those parts of the ROM files, so I am hesitant to start over yet again and I think I am going to try to adjust what I have if possible (using BlizKick). The first two times through BB3 I checked the A1200 checkbox, but the last time I did a clean install, I left the "Other" check box checked. This might have made some difference, but none that I have noticed yet. I have never seen any scsi.device copied to Devs: during any part of the OS3.9, BB1, BB2, or BB3 installs. I now have install logfiles for each step along that path that I will send to you if I can find an email address for you. I don't know how to send attachments with PMail here. I will also send you my old Startup-sequence file, but I don't know if that is going to help any.
I have BlizKick downloaded and have been reading through it's guide. Is there any advantage to using LoadModule over using the parts of BlizKick that do the same functions? If I can master BlizKick, I think I will try to rip my 3.1 ROM image, split it into modules and then reassemble a patched ROM image and map it to Fast RAM using the Blizzard MapROM feature and instructions within the BlizKick guide. I am hoping to get it so it will not have to reboot twice, but will still be able to run Shapeshifter or Fusion and will boot as fast as possible and run a stable, patched OS3.9 system as fast as is possible.
This has turned out to be more work than I thought it was going to be, but I don't mind as the goal will be a rewarding experience to use. I am sure that it must be something I am doing wrong during the installation process of OS3.9, and all of the BoingBags, but I don't know what it is yet. I should have run all of them in Expert mode I guess, so I could have seen and controlled more of what was being installed. I did not see any instructions for BB3 that recommended that the clean install of OS3.9 and BB's 1 & 2 should be installed using Expert, or even Intermediate mode instead of Novice mode.
If your email address is not easily available here or elsewhere, send it to me so I can send you my log files and startup-sequence.
Thanks for the offer to look at them and to try to help.
Edit: @Framiga, the results are scsi.device 43.43 and I meant to say that I have no scsi.device copied into my Devs: directory, not that I don't have any scsi.device at all.
-
I have BlizKick downloaded and have been reading through it's guide. Is there any advantage to using LoadModule over using the parts of BlizKick that do the same functions? If I can master BlizKick, I think I will try to rip my 3.1 ROM image, split it into modules and then reassemble a patched ROM image and map it to Fast RAM using the Blizzard MapROM feature and instructions within the BlizKick guide. I am hoping to get it so it will not have to reboot twice, but will still be able to run Shapeshifter or Fusion and will boot as fast as possible and run a stable, patched OS3.9 system as fast as is possible.
Yep that's what I do, just use BlizKick instead of LoadModule and build a BB3 ROM to be copied to FASTRAM on startup ;)
-
@amigadave
Blizkick can be a bit confusing/intimidating at first glance. But you can basically copy the loadmodule module line over, and use there rest of the patches after the kickstart has been saved with saverom, the documentation explains it very well. Modules like FusuionReverse ( i believe its called) are shapeshifter specific , or mac emulation..
Hey if you figure out how to get shapeshifter running fast, please holler... I´ve tried 7.1 and 8 i believe, and they all ran slow as feck... Using a 512 meg image... I wonder if creating a partition would be better..
But again, the problem i ran into, was that i kept dropping in certain versions of libraries and devices.. Which is really scary if you have stuff over 4gigs.. I ended up with a 5 step reboot, but thats fine given the speed, and functionality. Say i dropped the morelibspace REBOOT, it should have worked with os3.9 without a reboot, but that screwed up my scsi.device, exec, and workbench.library.. Also try out various 68060 libraries, the unofficial ones on phase5.a1k.org/ gave me a substantial boost over various others, however, i think the latest mmu libs are are as fast if not faster, and with of course, various fixes no doubt.
I´ll post the beginnig of my startup-sequence once i have the linux box running again.. Maybe someone can give me some pointers.
-
Hi all, great topic! I've got a quick question: what are you all using to do benchmarks with? sysinfo? sysspeed (which doesnt run on my machine, for some reason) or AIBB? do they also serve as a 'stability test' ?
-
Yep that's what I do, just use BlizKick instead of LoadModule and build a BB3 ROM to be copied to FASTRAM on startup ;)
Okay, I finally was successful in installing OS3.9+BB1+BB2+BB3 and added the lines to my Startup-Sequence without any errors showing up after a cold restart. Hurray!
I don't know why this is true, but it only worked after I used Expert mode in the Installer program of BB2 and BB3. The missing scsi.device DID finally show up copied to my DEVS: drawer so it could be loaded with LoadModule into Fast RAM.
I did add one thing to the lines that are suggested to be added to the Startup-Sequence. Before the command "NOREBOOT" at the end of the LoadModule line I added the command "FAST", after I read the guide for LoadModule a little bit. Maybe it was an unnecessary addition and the LoadModule command puts everything into Fast RAM anyway, but I added it anyway and I think I got about 200k of Chip RAM back after my next reboot after doing that. Since LoadModule is now working, I am not sure that I will switch to BlizKick, unless someone here can give me a good reason to do so. I still might use it to build a custom ROM file on this A1200/060 if I can understand the advantage of doing so over the LoadModule method. I want to learn how to use it anyway as I have a 4mb KickFlash board I am thinking of using on my A4000T and will need to build a Kickstart ROM file for it in the near future.
I also looked at the speed optimization suggestions and unarchived the PatchFor020+ files and read how to use it. It is not for the faint of heart and certainly not an easy install as you have to manually run the patch on what ever files you think it might provide a speed increase for. There is a list of which ones it should help and directions on how to use it, but I am not sure it is worth the effort, so I would appreciate any comments from those that have used it about how much of a speed increase they have noticed, or have test results of how it has worked on their systems.
Before I started my latest install of OS3.9 plus all the BoingBags and extras, I downloaded SFS and changed the file system on the partition I have been using to test these installs of the OS and BB's and I think that just that one change has made a very noticeable difference in performance. I think I will now change the file systems on all of my partitions to SFS, or I might dig out my copy of PFS3 and try it on my other boot partition instead of SFS to later do some speed comparison tests between the two boot partitions after I get one boot partition set up just the way I want it I am going to copy it over in it's entirety to the other boot partition, sort of a mirrored boot partition to use as a backup in case one of them becomes corrupted (which is not supposed to happen on SFS, or PSF partitions).
I am enjoying working on this A1200/060 more than I thought I would. After working with a fast and very nice looking and full of extras Amiga emulation using Amikit on a Quad Core 3.0GHz PC, and running MorphOS2.4 on my 1.5GHz G4 MacMini, I did not think I would enjoy OS3.9 on an 060 A1200 without a 24bit graphics card as much as I am. The challenge of getting the most out of this old hardware is very rewarding, even though I have spent a lot more time on it than I had planned and still have many more hours to spend before I have it finished, but I am getting closer and can see the light at the end of the tunnel now. I have to test it on at least one more monitor to determine if my IndivisionAGA is faulty, as I have not been satisfied with the display's stability so far, either using NTSC monitor driver, or the HighGFX driver, but I hope it is just that the two old CRT's that I have tested it on so far are on their last legs and that it is not the IndivisionAGA, as I have heard nothing but great reviews about it from friends who have them too.
Edit: @Mike, I used to run MacOS7.5.3 on my A2000/030@33MHz and it didn't seem to bad for the time. I am pretty sure I had it using my PicassoII graphics card, which I am sure helped it a lot. Back in the day (hate that term) I could brag to my two sisters who were Mac users about how I could run MacOS7.5.3 faster than they could while still running AmigaOS and Windows on my Bridgeboard all at the same time.
@rvo_nl, I don't know what speed test software to use after I get everything set up the way I want it, but hope someone here will give us both some suggestons. I know that sysinfo has gotten lots of bad reputation for being inaccurate, so maybe sysspeed will be a better choice. I have no experience with AIBB, so can't say anything good or bad about it.
-
hi amigadave, thanks. hope to hear some suggestions from others. sysspeed is working for me now, after I reinstalled MUI. BTW, I know exactly what you're talking about regarding getting the most out of old hardware and how rewarding it can be. I've still got a long way to go myself, but it's still fun to keep trying :) Good to hear you've got the 3.9 + Boing Bag installation sorted, it took ages for me aswell!
-
@amigadave
SpeedyIDE ( speeds ide by 5-10 times) , SpeedyCHIP, fusionreserve ( replaces a shapsehifter patch), quickboot ( removes the lsd boot display, and should be seconds quicker, i thinik), noclick , and localfast i believe saves chip , speedychip is not necessary though.. its been replaced by other patches . im working from memory so.. read up :> good to hear you´ve got her up.
-
ftext causes screen corruption when dragging icons. some icons appear corrupted when I start dragging them. Any ideas?
could someone who managed to have a perfect AGA wb with boingbag3, mcp, fblit ftext, blazewcp, systempatch3.3 post his startup-sequence and user-startup? Also the versions of patches, etc used.
-
ftext causes screen corruption when dragging icons. some icons appear corrupted when I start dragging them. Any ideas?
could someone who managed to have a perfect AGA wb with boingbag3, mcp, fblit ftext, blazewcp, systempatch3.3 post his startup-sequence and user-startup? Also the versions of patches, etc used.
See my original post on this thread ;)
-
I'd like to know where did you find those nice glowicons.
-
Re faster (http://www.fasterthanthem.com/)I dont think its as fast as they claim
-
Hey Amigadave + others
So can anyone report their finding with Cybergrafx4 AGA driver please? is it better than the commodore driver? ?
btw cool thread :)
-
So can anyone report their finding with Cybergrafx4 AGA driver please? is it better than the commodore driver? ?
I thought it was working just with CGX3 and ditched on v4?
-
I did this a few years ago, actually, and AmiKit decided to cause lots of dramas for everyone, getting various people's sites shut down left and right even after the Kickstart was removed. (Including, as it turns out, a medical forum, etc. ie. stuff which had nothing to do with Amiga.) He sees himself as some kind of "Cloanto representative" since he is getting paid by them to shut down sites.
Umm considering that Cloanto paid good money for the rights to the kickstarts they have every right to shut down sites that give them away. So if by "drama" you mean punishing people that are freely distributing copyright materials then sure...
I like everyone else would like free kisckstarts. One of the main features of Amiga Forever is that it comes with kickstarts. I even used my CD with OS 4.1 u4 and the built in Run UAE.
Great thread btw
-
Ok I finished playing around with my new 1200's setup, now up to 128 colors and still nice and fast.
AGA only screen shots (800x600 SuperPlus Indy Mrk2 + Ken's excellent ICONS).
(http://home.iprimus.com.au/novacoder/IMAG0212.jpg)
(http://home.iprimus.com.au/novacoder/IMAG0211.jpg)
(http://home.iprimus.com.au/novacoder/IMAG0207.jpg)
-
Whao! love the clean classic setup! I guess your on a 060 now and the original 030 was too slow? I just got my v3.1 roms cant wait to try a higher WB revision for my a1200 :)
-
Thanks, I like to keep it pretty simple. The more patches and hacks you install the less stable everything is. When my programs crash I like to know if it's really my fault or not ;)
Yep the 060 helps for sure, I'll upload a video when I get my new camera.
-
When I use superplus screen mode and 3.9 with indi MK2 on my 1200 the screen flashes black when clicking drawers etc so I stayed at 3.1 instead :(
What do you use?
-
Peter K's awesome new icon.library :)
-
I guess Peters Peter K's icon.library is available somewhere over at EAB.. Just had a quick google now.. Looks pretty sexy but still blends in quite nicely with the overall desktop!
-
@all
Sorry but... cybergrafx on AGA?
@novacoder
nice wb
-
@all
Sorry but... cybergrafx on AGA?
Yes, there's a CGX driver for AGA, although I don't think it improves speed much compared to the typical patches. When I heard about it I thought "kewl! I'll have a Ham8 WB and will be able to run some apps in CGX 15bit screens!" but it doesn't have R5G5B5->ham8 support :_( Ham8 screens were slow in Fusion but quite cool.
The best thing to avoid slowing down your miggies is using screenmodes that don't use too many DMA channels: e.g. AGA 640x480 flicker free in more than 16 colours will use too many dma channels and will slow down chipmem access (no matter how many patches you use to make the problem less noticeable, the problem will remain there), AGA SuperHiRes screenmodes act like those productivity screenmodes, more than 16colours will slow down. 15Khz HiRes on AGA is no problem regardless of the number of colours (blitter will need more time to blit due to the higher number of bitplanes but cpu will be able to access chipram at full speed).
With OCS/ECS anything HiRes in more than 4 colours will slow down your miggy, MagicWB makes little sense in OCS/ECS machines. If I could choose an iconset I would use 1.x-style icons for OCS/ECS machines since the icons looked great (I love the white rabbit jumping over the turtle). For apps I would use separate screens with normal 2.x/3.x colours.
-
Crumb
Interesting post. I disagree with the part about magic workbench on ocs/ecs. MB works very well for me with lower speced machines..
What about the new MK2 modes like Superplus and those? How fast is chipmem access?
And the most important question why do you have an avatar with Satanic imagery? Thats quite offensive and i'm sure against the TOS