Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: sim085 on July 03, 2009, 08:50:07 AM
-
Hi,
I am installing WHDLoad. I had already done this in the past but I thought of trying this again. I am installing WHDLoad from WinUAE at the moment.
The problem is this; When I set the processor to type 68000 WHDLoad fails to install. However if I set the processor to type 68020 (or higher) I can managed to get WHDLoad install. After installation I can set the processor type back to 68000 and games work just find (example: lemmings).
Does this mean that on real amiga hardware WHDLoad would need a 68020 processor to be installed?
Regards,
Sim085
-
No.
A bare 68000 is enough for installation and running at least 50% of all slaves, only if you have enough RAM (1Mb CHIP and 2Mb Fast is a working config for A500). That's a functional setup, not an ideal.
68020 would make system more responsive in terms of overall speed and it would allow all WHDLOAD games to support quiting back to OS.
Can you quote error message ?
-
According to the WHDLoad manual, the minimum requirements are a 68000, Kickstart 2.0 and 1.0MB of RAM. Some games will require more though.
--
moto
-
Can you quote error message ?
Here is the error I get when processor is set to 68000:
Installer
Program failed (error #80000003)
Wait for disk activity to finish
If I set processor to 68020 (or higher) I do not get this error!
-
Which kickstart rom image are you using?
-
Which kickstart rom image are you using?
Kickstart 3.1 but if you want I can test with Kickstart 2.1 as well (I do not have others however).
-
You have wrong version of Installer (compiled for 68020).
Get this one:
http://aminet.net/util/misc/Installer-43_3.lha
-
You have wrong version of Installer (compiled for 68020).
Get this one:
http://aminet.net/util/misc/Installer-43_3.lha
Thank you for that. I downloaded my installer (WHDLoad_usr.lha) from WHDLoad website, that is here: http://www.whdload.de/. I did not know there where different versions for different processors.
Could this mean that even though when I changed the processor back to 68000 lemmings works fine, I could find games that actually do not?
-
Yes, you could.
Some WHDLOAD installs are compiled to run at 020 as minimum, some require rare 010 for so called VBR support which you cannot get on plain 68000.
I have found at least 2 games from my personal interest (Amiga Karate, F/A-18 Interceptor) which failed to run on configuration similar of your own. The issue was resolved as slave/install author was kind enough to re-compile stuff compatible for 68000. However, I find that a rather exceptional case, not a common among a niche of WHDLOAD slave/install authors.
At the end, at least you got one more reason to start over getting A500 accelerator.
Or switch to A1200 which is, hands down, a WHDLOAD gaming champ, right from bootstart.
-
Some WHDLOAD installs are compiled to run at 020 as minimum
Hi, I think I just found such a game! I tried to install Colonization WHDLoad version. When I try to start the game I get an error that this program needs at least a 68020 processor.
I do have the original version however installed on the real amiga hardware which only has a 68000 processor. Does this mean that if I want to use the WHDLoad version then I'll have to recompile it?
-
Yes, but honestly I don't see you doing that alone.
That's way over your league (me included!) and your best bet would be to contact author if he can reconsider recompile for 68000.
-
I may try to do that. Not because I need it (I have the original disks which work fine on the 68000). It is more because in my opinion this game worked perfect under a 68000 processor. However maybe it needed a more powerfull processer when working under WHDLoad.
However isn't one of the goals of WHDLoad to make games work the same on all the different processors and kickstart versions?
-
I do really admire your determination, even if it's bound to fade abrupty when you actually realize what WHDLOAD slave writing is all about.
Back to the topic, WHDLOAD does need some extra system resources since it's a OS wrapper. Games run on same hardware would suffer some speed loss, but I guess on plain A500 things are slow as default :) and thus little affected.
WHDLOAD tries to allow/recreate same or near same experience (with respect to original), but that's only an attempt being constantly improved from each new release. There are known limits (it won't work under Kick<2.0), and know issues (68040 is a bad WHDLOAD host choice, many games need additional tweaking).
In fact, I'm aware for few games which are too fast on my 030, but that can be handle by smart slave option set.
-
I do really admire your determination, even if it's bound to fade abrupty when you actually realize what WHDLOAD slave writing is all about.
There is no shame in trying and failing (which is what will most probable happen). Just another question. To install the new installer I need to just replace the files inside my Workbench directory?
-
I might been a bit over the line.
Sorry for that.
Extracting file "Installer" from archive into "C" drawer would be enough.
-
I might been a bit over the line.
Sorry for that.
Not at all :) I know this stuff is very hard. I really admire the people that actually managed to first understand and then make all this stuff work :)
Extracting file "Installer" from archive into "C" drawer would be enough.
Thank you for that, you can see what a big newb I am from the questions I ask :) but I keep notes, and therefore I learn!
-
Extracting file "Installer" from archive into "C" drawer would be enough.
I did this, however it still gives me the same error. Also I noticed that in C I have another file called install. However I went on the Install icon and went to Tools > Information and here it says that the Default Tool is Installer.
However as I said I still have the same problem! :(
-
Hi,
sorry to bring this up again, but cannot manage to understand how to make the installer of WHDLoad use the installer tool I moved in C:
Also when I moved the installer tool there was no previous installer tool in C: there was only an install tool. However the Default Tool for the WHDLoad installer is equal to "Installer" but do not know what this means!
-
"Install" found in C: is part of Workbench command set. It's used to write bootblock, something not even remotely connected to your issue. Forget about it.
Let's see if you have stuff set right at proper palces.
You should open shell and type Installer. If set correctly, you should get something like:
Installer 43.3 (30.4.96)
USAGE: Installer ...
Any other message, like "Installer: Unknown command" would mean Installer is not in path accessible to shell and thus to ToolTypes, too.
-
Installer 43.3 (30.4.96)
Yes I do get this result from shell. However when I double click on the install icon of WHDLoad I still get the same error as before:
Installer
Program failed (error #80000003)
Wait for disk activity to finish.
Do I need to start the installer of WHDLoad from shell?
-
Install and Installer are two separate programs. Be sure you have both since some
programs call on one or the other. AND...
Check to be sure the protection bits are set right. When downloading things from the net,
often these get messed up. In other words, make sure the important and obvious
files (like WHDLoad itself) you are playing around with are all "executable". When
doing an 'info' on the file, be sure that option is checked.
Not sure why else you are having all this trouble installing a simple program.
Should just be able to throw that program into 'C', place your key in 'S' (yes, you
should register this) and be done with it. Maybe an assign in user-startup pointing
to WHDLoad, but come to think of it, not even sure that's necessary. Good luck!
-
Not sure why else you are having all this trouble installing a simple program.
I think the problem is related with the WHDLoad installer (which fails to install under a 68000 processor but works fine on a 68020 processor).
I say this because the sample script works fine when I put the installer under Sys:C which means that this is installer works fine (with out the installer under Sys:C this would give an error)
I think I need to modify something in the WHDLoad installer! Is this possible? Maybe it is not using the new installer I just placed in Sys:C
-
I think that because you are using Winuae, it'll more likely be a Winuae config issue, try 68000 with an older kickstart image and see what happens..
-
I think that because you are using Winuae, it'll more likely be a Winuae config issue, try 68000 with an older kickstart image and see what happens..
I can not do that because I am using Workbench 3.1. Doesn't workbench 3.1 need at least Kickstart 3.1?
-
I was also thinking the following ...
I did not have any Installer tool before putting the downloaded one under Sys:C (I mentioned this in some post about).
So how come the Installer tool refered to by the WHDLoad install script has worked fine under the 68020 processor? shouldn't have it also failed because there was no Installer tool under Sys:C?
Not that my Workbench 3.1 is a fresh installation and did not havbe the installer tool under Sys:C. Is this normal? If yes, then where is the default installer tool of Workbench 3.1 located?
-
SYS:Utilities is another common place for Installer.
-
Just copy WHDload to your C folder manually.
-
Just copy WHDload to your C folder manually.
Ok, I managed to make the installer work. There was another 'Installer' tool in the directory of WHDLoad and it seems the latter used this one rather then the one in System:C! I removed the installer tool inside the WHDLoad and its installer started using the one in System:C.
SYS:Utilities is another common place for Installer.
Thanks, it seems that workbench finds the installer tool regardlessly if it is in System:C or System:Utilities! How does Workbench work in this regard? What does workbench do to find a tool such as installer?
-
Workbench attempts to search at locations defined through PATH command. PATH is invoked inside S:startup-sequence file.
-
Workbench attempts to search at locations defined through PATH command. PATH is invoked inside S:startup-sequence file.
Thank you very much :) I understand now. This is very interesting stuff ... I am looking forward to learn more on Workbench :)
-
To this day, I am still completely clueless on how to even use WHDLoad. I go to the site with various games for download and I see that they are only around 48kb in size. Game downloads are much bigger than that, so why these are only 48kb-100kb is unknown to me. If anybody can give me an idea on what to do please let me know. Thanks.
Barney
-
What you see are installers for games. You need the original disks to install on your HD.
On http://kg.whdownload.com/kgwhd/ you can download the whole Amiga Games package.
If you only want a specific game you can go to http://www.whdownload.com/ .
-
Thanks for the links amiga1260, but I have one more question. You say that if I only want to install one game, I need to download the game, adf it to disk and then install it on a hard drive? Is this correct or am I missing somthing?....This is why I find this WHDLoad so damn impossible to use.
Thanks.
-
No. whdownload.com already has "installed" games available for download. Simply double click on the games' icon and get ready for some serious fun!
The fact you can install a non-HD installable game using WHDLoad with your original disk is brilliant. That was the original design of the program. Was never meant to be a vehicle for piracy. OR am I being naive and was that feature just a clever disguise? lol In any event, it was inevitable that most of these whdload games would pop up publicly for download before too long.
-
That was the original design of the program. Was never meant to be a vehicle for piracy. OR am I being naive and was that feature just a clever disguise?
Pirates is available for download while SimCity is not! I always thought it was because for legal issues ... the title SimCity is still owned by Firaxis as much as I know!
.. or that is the reason ... or else I am naive as well?