@Spirantho

Quote:

Even so, -500,000 is not a good number of bytes to have left! Exec should have just refused the allocation....

It probably has done so, I suppose the free memory display is wrong. There had been a last minute fix to this since it used to show too much before that. This has something to do with the ... *coughs* uniqueness of the Amiga's memory layout (most memory banks are islands in a sea of empty pages). I'll investigate this.

_________________
Seriously, if you want to contact me do not bother sending me a PM here. Write me a mail

@stevieu

> As you mention, there are delays when dragging screens under those conditions.

Dragging non-AGA screens (on AGA its done via copperlists) on a gfx board requires
a copy of the screen. On the AOne the typical gfx board has enough memory for
the screen and the copy. On the classic Amiga the gfx board often has not enough
memory and the copy has to be stored in main memory and large transfers of data
from/to the gfx board result in a noticable slowdown.

With smaller screens or a smaller screen depth, screen dragging should be usable fast
on a classic machine too. The last time I experimented with it, it was possible to find
a max screen memory limit at which the noticable slowdown started, IIRC it was about
half the size of the gfx board memory.

Prefs/Workbench has an option to display the free gfx board memory in the WB titlebar.

@stevieu

Quote:

Despite the Mediator/Voodoo combination having slower bus speed, I'm still pretty sure things are running slower than they should be

The Mediator/Voodoo combination is about factor 6-8 slower than the BlizzardVision. The BVision is directly connected to the Blizzard via a local bus. Add to this the fact that every time the voodoo needs to access one of its registers (as opposed to the framebuffer) there is going to be a pipeline-stalling exception to slide the Mediator window to the proper position. Nothing to be done about it, the MMU "trick" *is* slow. Try with a BlizzardVision and you will see the difference.

Quote:

As you mention, there are delays when dragging screens under those conditions.

The draggable screens come at a price. Normally, graphics cards can't do this like the Amiga could.

Quote:

If I open, say, Ibrowse on a separate screen for example, dragging windows around on the Workbench screen (in solid mode) is extremely slow. Maybe I'm expecting too much hehe and this is just a limitation of the hardware.

Dragging screens is done by copying if I am not mistaken, so there is no suprise it is slow.

Quote:

Still, the graphical corruption issue that is known about. I note, when I run AmigaInput, Showconfig, or AmigaAmp and more (or if a GrimeReaper is invoked) the graphical corruption renders Workbench useless (icons disappear etc) and a warm reset is needed.

I am on this. Unfortunately my A1200's keyboard adaptor is no longer working, so I cannot test it myself but have to send kernels around and wait for the feedback, making progress on this noticeably slower.

Quote:

ED - time for a few pints of Leffe tonight, methinks. Cheers, Rogue!

Recently, I seem to be drinking mostly cranberry-flavored mineral water..

_________________
Seriously, if you want to contact me do not bother sending me a PM here. Write me a mail

Has anyone had any luck with either a TV or sound card on the Mediator?
Has anyone tried installing a powerflyer/FastATA interface?

Have had a go at the sound and TV card but got nowhere so far.
I suspect the sound problem could be down to the driver for the Terratec 512I I have installed.
The TV problem appears to be related to the gui for both programs I have tried.

Had the FastATA software installed but the was an error message on bootup.
Although to be honest, I hadn't followed the installation process properly.
I should be in a position to do that on Saturday.

_________________
If your nose runs and your feet smell, you're upside down.

@TiredofLife

iirc, any PCI card that needs mediator DMA access will not work under os4.

_________________
AmigaOne X1000

@Spirantho

Sorry, but OS4 on Classic is as stable as A1 version running 68k apps. It's not unstable copying many files. Check out your PSU and heatsink/cooler. Increase the amount of ram to 128MB. 64MB is a joke, but some developers used it while they developed OS4 so I'm pretty sure it doesn't have problems. Dragging down AGA screens doesn't crash the system, just like dragging down RTG screenmodes doesn't crash the system either.

I think you should remove your old Oktagon as it is very slow compared to the uwscsi controller of your CSPPC and does not offer any advantage. In contrast, it makes your PSU work harder.

Check out your hardware because it's not working correctly.

BTW, PC-Task works on A1 with OS4. A friend of mine uses it with OS4-Final on his microA1.

Last edited by Crumb on 13-Dec-2007 at 02:44 PM.

_________________
The only spanish amiga news web page/club: CUAZ

.

Last edited by Framiga on 15-Dec-2007 at 12:27 PM.
Last edited by Framiga on 13-Dec-2007 at 03:09 PM.

_________________

@Crumb

Thing some did say that if you disabled, JIT emulation you saves lots of RAM, maybe a good thing to do on 64Mb system, I think the best thing to do is to upgrade 128, if possible to 256MB,

I have been running on 256MB for long time whit any problem.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

Four cannals, I must have hibernated for too long !!!!. When the fek did OS4 Classic come out ??? WOW !!!

£60's not bad... hope it'll run on my Classic Miggy:
http://newton.sunderland.ac.uk/~specfreak/MyAmiga/MyAmiga.html

Fantastical.....

@ddni

They do, you just need to us the drivers provided with the hardware.
In my case, I use the Elbox drivers that came with the Mediator.
So far I have USB, Graphics and a Network card working under OS4.

_________________
If your nose runs and your feet smell, you're upside down.

@Framiga
I used to use PFS3 as well back in the day and it was (note the past tense) superior. It really is inferior to SFS now. Joerg has done an excellent job of bullet-proofing SFS and adapting it to the latest DOS API which is something that will never happen with PFS3. You are taking a huge risk sticking with PFS3 any further because AmigaOS has moved on and PFS3 is stuck back in time along with its hacks and workarounds for things in DOS that have been fixed now. There is absolutely no point in using it any further.

_________________
ExecSG Team Lead

Too bad. My Cyberstorm stopped recognising hard-disks yesterday, one minute before I tried to install OS4 :(

At bootup it does not scan scsi.device, even though I did not use scsi patch. It does not scan the uwscsi bus, which worked perfectly before.

Anybody has had a similar problem? Time for a reflash?

@stefanor

Quote:

Too bad. My Cyberstorm stopped recognising hard-disks yesterday, one minute before I tried to install OS4 :( At bootup it does not scan scsi.device, even though I did not use scsi patch. It does not scan the uwscsi bus, which worked perfectly before. Anybody has had a similar problem? Time for a reflash?

Maybe all SCSI units are disabled (by some accident) in the FlashROM settings?
Press ESC during boot and check the settings.

@TetiSoft

Quote:

Maybe all SCSI units are disabled (by some accident) in the FlashROM settings? Press ESC during boot and check the settings.

All the connected units are active in the Cyberstorm SCSI menu, I checked...

@specfreak

Well you have a top-of-the-range Blizzard so no problems there!

Only the SCSI won't work, which is why I've ordered a Buffered IDE interface with OS4.0 from AmigaKit - just to get me going!

I'm not going to like using IDE disks through the 1200 mainboard (always been a SCSI fan before for many reasons) but it's a case of anything to get me going

I should be able to access any files I need through the network via the PCMCIA ethernet...

@Crumb

Quote:

Crumb wrote: @Spirantho Sorry, but OS4 on Classic is as stable as A1 version running 68k apps. It's not unstable copying many files. Check out your PSU and heatsink/cooler. Increase the amount of ram to 128MB. 64MB is a joke, but some developers used it while they developed OS4 so I'm pretty sure it doesn't have problems. Dragging down AGA screens doesn't crash the system, just like dragging down RTG screenmodes doesn't crash the system either.

Oh, I think most things are fine with it, I'm just reporting the occasional trouble I've had. No criticism or anything.

Quote:

 I think you should remove your old Oktagon as it is very slow compared to the uwscsi controller of your CSPPC and does not offer any advantage. In contrast, it makes your PSU work harder. Check out your hardware because it's not working correctly.

I don't have anything connected to the Oktagon - one SCSI chip on a Zorro II bus won't overload the PSU.

Quote:

BTW, PC-Task works on A1 with OS4. A friend of mine uses it with OS4-Final on his microA1.

Strange, it's never worked on mine, just calls the Grim Reaper. Maybe he's using a different version of something.

I don't want you to think being I'm being critical of OS 4 - I'm not - they've done an amazing job - but to say there are no bugs in it... well, Hyperion would be the first to agree that there are. I'm just trying to report the problems I have found with it.

As I see it, though, given my setup works fine under OS3.9 obviously I'm going to suspect OS4 when something like the freezing happens. If anyone wants more details of my set-up, obviously I'll provide. But I have tried different cables, different disks, different terminators etc. The PSU is fine because I even took out one of the disks once to make sure. I also tried with 64MB RAM as I mentioned earlier just to be sure, same thing. The PPC is fine because I left it running a 68K Spectrum emulator (i.e. an emulator emulating an emulator!) and it was perfect.
I'll keep messing around with it, but obviously I'll report any other OS glitches I find (it's what I'd want if I were Hyperion....)

Edit:
It's not just copying files. I just did a slow format on a 700MB partition and it froze solid half-way through.
It's consistent! If it were termination, it'd just give errors. If it were PSU, it'd fail under AmigaOS 3.9.
Maybe the SCSI is slightly iffy on my CSPPC or something? But I've had no trouble under 3.9....
Need to try a different device....

Last edited by Spirantho on 14-Dec-2007 at 04:21 PM.

@all

Well, I thought I'd reinstall AmigaOS4 and try it out with my BVision instead of using the Mediator/Voodoo setup (as I think I may stick with it for now) and change HDD.

Everything works fine up until the final part of the installation, where I get the error;

'Configuring your new system configuration. This will only take a few moments.
Copying language preferences.
No language preferences selected, you should do that after booting your system. Copying default preferences.
Error copying standard preferences files.'

I did select language preferences during installation.

On exiting the installation and after doing a warm reset, I get the error;

:C-68k/version unknown command

it resets and that's that. I'm not sure what's happening!

[ED - Duh, I forgot to turn the Amiga off for 15 seconds to rid of the installation kickstart from memory.... Still not sure why it failed to copy the language preferences though, on every occasion I tried.]

Now I get an endless reset. Will keep on fiddling :)

Steve

Last edited by stevieu on 14-Dec-2007 at 06:35 PM.
Last edited by stevieu on 14-Dec-2007 at 03:10 PM.

_________________
A1200T - OS4.0,OS3.9: 603e PPC 200mhz,060 50mhz, 256mb ram, FastATA MK-III, BVision, 160gb,20gb HDDs

A1200 - OS3.1: Blizzard IV 030, 64mb ram, 400mb HDD

OS4.x - Flying the AMIGA flag

@stevieu

Copy a "version" command from OS3.9, C directory

Or try to find the 680x0 version on boot disk or install CD.

C-68K = Commodore 680x0?

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

Unfortunately i can't get my RepulseGold working :-/ ... still tweaking

Last edited by Framiga on 15-Dec-2007 at 12:28 PM.

_________________

@stevieu

Quote:

Error copying standard preferences files.'

Make sure the disk you install on is empty. This error usually occurs when you try to install over an existing system.

_________________
Seriously, if you want to contact me do not bother sending me a PM here. Write me a mail