Amiga questions you've always been too embarrassed to ask

[Paulee_Bow]

Hello I thought of another question

My A500+ originally had Kickstart 2.04. The initial upgrade involved me buying an accelerator with a fast 68000 and IDE. I installed Workbench 2.1 and all seemed to go well.

Some of the music software I wanted to run demanded Kickstart 3.1...so I purchased the chip and installed.

I didn’t want to really mess up my nice 2.1 installation, and all the troublesome software now works, so WB2.1 on 3.1 ROMs is totally doable, apart from ONE NIGGLE.

It’s a minor thing, but in this setup, WBpalette doesn’t seem to properly save its prefs. When I boot up, I get the dull grey and blue. Going to the palette program in the prefs drawer and opening it magically brings my colours back again. All is good until the next boot where I have to manually run it again to get my colours back.

So far I’ve just dragged a copy of WBpallette into the WBstartup drawer. On bootup the right colours come up but I have to click on “save” or “use” and it’s not the most eloquent solution.

Can you think of any better solutions, ideas I had:

- Nicking a copy of WBpallette off a Workbench 3.1 disk and seeing if that works, though some libraries might not be right and it could get messy!
- Adding a line to the startup-sequence that both runs palette and automatically tells it to save, like I’ve clicked the button.

Any ideas, let me know, it’s the most minor niggle ever, and I can totally live with clicking save manually, but I’d like to see what’s possible.

[daxb]

I don't know how OS2.1 works but on 3.1 IPrefs is responsible for loading WB settings. Maybe 2.1 doesn't have IPrefs or works different? Check also if the place and name of the saved settings file is equal or different. The format should also not differ.

[demolition]

I'm guessing you have some invalid palette prefs file somewhere inside ENV:. At runtime ENV: is located on RAM: but you need to put the correct prefs file on your WB disk where the files are copied from (or just delete the file so it will create a correct one the next time you press 'save'). I don't remember the filename, but perhaps something in the lines of palette.prefs?

Or perhaps the prefs file had become read-only for some reason which means that saving won't overwrite the file.

[Hewitson]

I would just upgrade to the proper OS version. You're missing out on quite a few nice things.

[Gorf]

Originally Posted by van_dammesque

OK my first question in this thread! I bought this for £6ish? With my Apollo 040 25Mhz in my A1200, my question is what programs/tests showed the patcher working? I ran with and without but didn't notice ANY difference (including running Doom etc...)!

this is about Oxipatcher (and similar)

This only concerns programs specifically compiled for the 68020(30)+68881(2) combination.
Apps and games, that are already compiled for the 040 need no patching of course - the work has already been done at compile-time.

Software that is just compiled/crafted for the 68000 also needs no patching, as this only concerns cpu-instructions the above combination provided, but were no longer supported in the 040 und 060... the plain 68k instruction set was always fully supported (until coldfire :-/)

[zipper]

Differences with 040 are pretty small, 060 is a different case.

[Paulee_Bow]

Originally Posted by Hewitson

I would just upgrade to the proper OS version. You're missing out on quite a few nice things.

Might do at some point. For now, I can happily live with it for now, I’m just thrilled I have a working Amiga in 2018!

Just to clarify, the pallette program DOES remember my workbench colours, which I’ve picked as a tasteful muted teal and pale pink, it brings them up as soon as I click on the pallette program, it’s just that it doesn’t automatically do this when I boot up the machine, workbench is grey and blue which looks bloody horrible. I’d take 1.3 colours over that lol.

[NorthWay]

Originally Posted by NorthWay

I'm pretty sure the RISC-V stuff that Hennessy and Patterson talked about during their Turing Award ceremony said they had done ASICs for $14,000 for lots of 100.

Watch [ Show youtube player ] around the 57m mark to see this quote. (I suggest just watching the whole thing as they are excellent and interesting speakers!)

[van_dammesque]

RE: Oxy...
oh I feel ripped off now! Thanks for the info

[retrogamer]

How do I make a dump by a copy protected amiga game disk?

I own a A600 with a CF-card.

[idrougge]

If it's copy protected, it's copy protected. The entire point of copy protection is to forbid dumping.
If you have a 020 processor or higher, you could use Kryoflux Free.

[Mikerochip]

Originally Posted by idrougge

If it's copy protected, it's copy protected. The entire point of copy protection is to forbid dumping.
If you have a 020 processor or higher, you could use Kryoflux Free.

I just started using this! And it's super! But what stumped me for a while is it wouldn't dump disks where the write protect tab was open! Just a small tip


But I do have a question too!

How do I create a shortcut to KingCON?

I see in the readme, it says open shell, and launch it from there. But is there a way to launch it directly? I'd like to leave it out on the desktop, with it's own icon.

[idrougge]

Just drag it to the desktop and snapshot it.

[Jope]

Originally Posted by idrougge

Just drag it to the desktop and snapshot it.

Select it by clicking once, then select Leave out from the Icon menu.

[daxb]

Just add a hotkey for it then you don't need to use the mouse for it.

[Hewitson]

Originally Posted by daxb

Just add a hotkey for it then you don't need to use the mouse for it.

Dont need to anyway. Amiga+E and typing CLI is how I've always done it under 2.x/3.x.

[daxb]

Change hotkey Amiga+E or any other to open your Shell is much better/quicker. If you always use Shell then let i start with WBStartup. The easier the better.

[Daedalus]

Yeah, I always have my shell set to RAmiga+H. RAmiga+E is still useful for executing one-off commands.

[Mikerochip]

Originally Posted by idrougge

Just drag it to the desktop and snapshot it.

Originally Posted by Jope

Select it by clicking once, then select Leave out from the Icon menu.

Thanks! But! What's the 'it' that I select?

I know how to snapshot it, and I know how to leave it out, what I don't know is what to do those things to!

[idrougge]

Do it to the shell icon.