I'm in the process of installing OS4 now.

One problem I've encountered is corrupted graphics e.g. missing, mis-coloured/aligned gui elements and multicolour horizonatal banding. Anyone experience this. I would get similar problems in OS 3.5/3.9 if images were loaded in fat mem when using native screens. Otherwise things are going relatively smoothly (at 38%.)

@TiredofLife
I am also worried about this Mediator LT issue as I have one also.

Can I confirm you have used the elbox system files? Do they work as I may have to use them in any case as most of my PCI hardware is incompatible with OS4, I can't really live without networking.

If so what is the instalation process, the same as OS 3.x?

Many thanks.

@TiredofLife

start whit out startup sequence.

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

@TiredofLife

Quote:

Did you sort out the Voodoo problem and if so how?

From posts on this it would appear that there is an issue witht the Mediator Lt and I await Rogue's deliberations on this. The only use of the board it seems is for use of a graphics card but my Bvison works fine and OS 4.0 runs very smoothly when up and running. Unfortunately I cannot remove my Mediator as it provides power for my D Box and also if I switch to my hard drive with OS 3.9 it makes use of the other pci boards.

I think it's a pity that Elbox do not seem to have been very active and prepared for the release of OS 4.0. Had I not had a Bvison I would not be a happy bunny as VGA output is not very satisfactory.

_________________
Member of Midland Amiga Group (MAG)

I can confirm the elbox drivers can be used to get video and networking working. (haven't tried sound yet)

To achieve this I commented out the resident voodoo.card device in my kicklayout and installed elbox's voodoo.card in libs:picasso96\. I did not have to change the voodoo monitor device (devs:voodoo) in any way.

The only problem so far is gui bitmaps are corrupted at startup but can be fixed by changing the gui prefs (but won't survive reboot).

@Dafs

I have installed OS4.0. Everything seems to be working...ish.

I used P96Mode to get the correct resolution for my monitor, but I'm still getting graphic corruption on the title bar and gui elements. If I run AmigaInput (amongst others) my Workbench gets trashed and I have to reboot.

I have read that this has happened to a couple of other Voodoo/Mediator setups.

I don't want to install Elbox drivers unless I know it's safe

Other than that...it's nice to see OS4 in action at long last

Steve

_________________
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

I got graphic corruption throughout the instalation, but this was in the amiga native video modes. Mediator wasn't recognised at all (it's a LT4) so the elbox drivers were my only option, I got them going with no hastle.

Asside from corrupted bitmap pallettes I mentioned in my last post the Elbox drivers seem solid. However I do not know how the speed compares to Hyperion's PPC drivers. I assume they are 'safe' as I've had the OS running for about 2 hours now without a reboot and both me and my amiga are very much alive.

I say go for it if you can't wait for an official fix.

Anyone any idea how long until a fix for mediator LT4 is available?

The LT4 must the most popular Mediator board...

The lack of OS4 compatibilty with the LT4,(along with the lack of OS4 BPPC SCSI and DMA access) is the deal breaker that is STOPPING me from buying OS4....

_________________
AmigaOne X1000

@stevieu

So you need to change your signature

_________________
ikir

@Amigaz

Quote:

Nope, but gonna plug hook up another monitor to my scandoubler, the scandoubler on my PIV died a month ago :(

Use the original "PicassoModeTNG" to reconfig your scandoubler and it will probably resurrect.

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

If you got wrong colours, on your meditaor, try to change the palette prefs, just change a color a bit and save. this sould correct the problem. Altest ist does for another user who hast the same problem. He made a script wich replaces the palette after the boot automaticly.

_________________
www.brevis-design.de

@Mangaclub

Do you know if hyperion are working on a fix for this?

@Dafs

if you can confirm this then i might add a bugentry.

_________________
www.brevis-design.de

@Mangaclub

The nature of corruption varies with the depth used. I have included the following screenshots to demonstrate.

16 bit

24 bit

32 bit

Most of the time changing your prefs so that the workbench screen is forced to close and reopen wll solve the problem but must be repeated after every reboot. Sometimes changing the screen mode fixes it but sometimes it will make things worse.

The graphics adpter is a voodoo3 2000 PCI on a mediator 1200LT4. I am using the latest elbox mediator drivers. As the LT4 is not currently recognised by OS4.

Aditionally I think I have found onther bug. When using the gb and gb_ISO-8859-15 keymaps with elbox PC-Key1200 adapter the # (shift ~) key doesn't work. In the keymap file it is mapped to key 2B, I have found mapping it to key 0D solves the problem though.

Last edited by Dafs on 09-Dec-2007 at 12:41 AM.

@Dafs

I think you can fix the issue whit 32bit in GUI prefs.

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

Just wondering how fast and smooth it runs on th A1200 blizzard 200mhz with Bvision?

_________________
“Wouldn't it be much worse if life were fair and all the terrible things that happen to us, come because actually deserve them? So now I take comfort in the general hostility and unfairness of the Universe”

@Dafs

Quote:

Aditionally I think I have found onther bug. When using the gb and gb_ISO-8859-15 keymaps with elbox PC-Key1200 adapter the # (shift ~) key doesn't work. In the keymap file it is mapped to key 2B, I have found mapping it to key 0D solves the problem though.

Nice that you already found the solution

Documentation/Keyboards.doc describes the problem a bit, I'll try to explain it here:

The typical Amiga (non-US) keyboard has a 0D key, to the left of the backspace key,
when such a key is not present the backspace key is as wide as two normal keys.

The typical Amiga (non-US) keyboard also has a 2B key, to the left of the (lower half of) the return key, when such a key is not present the return key looks like a mirrored "L".

The typical PC PS/2 keyboard has a 2B key but not a 0D key.

An USB keyboard can have both keys, typically it has the 2B key only.

The mapping tables defined by MicroSoft for mapping USB keycodes to PS/2 keycodes
suggest to map both the 2B and the 0D key to the 2B key IIRC.

A keyboard adapter USB to Amiga should differentiate the 2B and 0D keys.

A keyboard adapter PS/2 to Amiga will probably always receive a 2B key event
and is unable to decide if that should be converted to 0D or not.

The Amiga keymap files are now in text format which makes it easy to correct
the behaviour of keyboard adaptors when needed.

@Dafs

IIRC in the A1200 Mediator version, you have 8 MB of video memory window ... is it correct?

Do you have available the tool AvailP96, to check how many video ram is free in the various resolution/depth?

_________________

Still no luck here :(

Same black screen with my Cybervision 64

I wonder if it's my Grex flashed CSPPC that's causing it...

_________________
A4000 CSMKII 50mhz
A4000 CS PPC 604e@233mhz '060@50mhz
A3000 '040@40mhz
A1200 '030@50mhz
A500+ '030@40mhz

@Amigaz

yes it is, please remove the grex flash and reflash it with the non grex.

_________________
www.brevis-design.de

Fixed the lockup problem.
Used the latest Elbox files and problem went away.

@Dafs
How did you go about sorting internet access?

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