I hope everyone's enjoying the latest incarnation of AmigaOS4. I know I am

Now this isn't meant to be a 'complaints' thread, I just decided to post my not so fun findings in a single thread because (Naturally) we are having threads popping up all over the place.

Beta testers & Hyperion, I've tried to put as much info on my system as I can here but there may well be some missing bits. One or two of these give me a GrimReaper. Now those make for LARGE posts so I'll PM the Grims if they are needed.

Graphics Things:::

> Amplifier - Some skins cause graphical glitches on the Workbench screen. Examples of my skins: Good skins = Base, Stella... Bad skins = Sony, Kenwood (Is this a Datatypes based issue?)
> Amplifier - Now this one JUST happened as I was typing this up. It was Iconified playing random tracks, one came on that I didn't like. When I double clicked the icon to bring back the window, the botton 70-80% of the screen had a mass of multicoloured pixels fill it (Like the noise effect of a TV, only in colour) & about a second after the screen went black. First time I've seen this & hopefully the last. Reboot only from here.
> E-UAE - I now no longer get a display either in Window or Full Screen mode, only a black screen & sounds
> Fonts - When overlapping, Anti-Aliasing uses the background colour rather than the colour of the overlapping character which gives the impression of an outline around each character (This can be (more) easily tested & seen using TypeManager & a bold font)
> Quake (Not the GL version) - The display is jumbled. Every 4 vertical columns of pixels are swapped... eg. 1234 5678 = 5678 1234 (Quite hard to explain)
> Earth 2140 - 800x600 is garbled wheras 640x480 works fine. Is this the Radeon I have? The menu screen on Earth 2140 also does the same thing as Quake as you scroll around the menu. Some frames are fine, some get the 'swap' effect as with Quake.
> Badger (The Hollywood demo) - Graphical glitches fill all but the left most, say, 25% of the window
> MysticView - Only the left most, again, 25%, id displayed correctly & the buttons (Top of the window) are garbled
> Zero (The first AmigaOne Demo) - Can't open a screen


Programs::: (I understand that these may be the app itself)

> GenesisPlus - Grims on run. I have had a few problems with previous updates but found that running SMSPlus first, then GenesisPlus helped out. It Grims everytime on me now.
> Heretic - Installation locks up just after explaining the serial code procedure (Similar issue to Freespace maybe)
> YAM - RMB menus sometimes take a couple of clicks before the menus show


Previous PreRelease problems that I have not yet had enough time to duplicate on Update 3 yet (Fingers crossed):::

> AmigaAMP - That annoying sound lock up & screeching (Not yet)
> FileRequest - Keyboard Shortcut for Delete & Rename not always working correctly (After update 2, update 3 seems fine)
> USB - When UBoot has the "Front Port" active, USBStart locks the system (Not tested this out yet)


This one's just weird:::

> Input - The numeric keypad "7" is sometimes locked on from boot up. You do not notice this until you go somewhere to enter some text (URL address, Notepad, execute command etc...). This was present in OS3.9. I've had it using OS4 Pre Release & Pre Release 2 (Quite rare, could be weeks before it happens again). I'll keep an eye open with Update 3.


If anyone knows of any solutions to these, that'd be great. If not & this for the moment just helps out iron out things for the final release, all good.

I will HAVE to finish up with; the list of things I am happy with FAR outweigh these few problems. Keep em coming guys

FuZion.

- AmigaOne XE-G4 @ 800Mhz
- 512Mb RAM (A1 tested)
- Radeon 7500
- Genius Keyboard & cordless mouse
- Network connected through a Router
- Fluffy Dice
- PlayStation 2 & Gran Turismo while I await replies

@FuZion

for your quake 1 problem (sw) .

Add the stack as normal and then use this line:

Quake_Os4 -IP -forcewpa8


forcewpa8 is the command u need.

_________________
See my blog and collection website! . https://www.blog.amigaguru.com

@FuZion

Earth 2140 ..

earth2140.exe x800 P96WritePixelArray smallpointers

u should read the manual....

(ps ...check your p96mode and that the res actually is active and works properly...if not...adjust it abit so it works.)

_________________
See my blog and collection website! . https://www.blog.amigaguru.com

@FuZion

Some of your problems could be due to non-updated software.
My configuration is similar to yours (A1-XE, G4 @ 800 MHz, 256 Mb RAM pushed to the max with SetA1 and RADEON 9000) and I don't have some of the problems you have.

Amplifier: no problem whatsoever here (it's playing right now) - I can send you the skin I'm using, if you want

E-UAE: I've already contacted Richard Drummond and he knows about this problems; he's working on an improved version already

MysticView: works just fine if you have the latest stuff (it's discussed also in this thread)

YAM: works perfectly here (latest dev build)

Input - The numeric keypad "7": never happened here, but then you have more fancy input devices than I


saimo

[edit: added link to thread]

Last edited by saimo on 15-Jun-2005 at 10:06 PM.

_________________
RETREAM - retro dreams for Amiga, Commodore 64 and PC

@FuZion

Good thread.


PhotoGenics 2 goes through loading modules etc routine and then .... Nothing.

FinalWriter ...............Nothing full stop

Thats all I've found out so far. You already mentioned AMPlifier with Nucleo skin problem.

Incidently, I use same skin with AmigaAmp and it has no problems? Except it gives a weird error message when you quit.



Spex

AmigaOne XE-G4 @ 800Mhz
512 mb RAM
Radeon 8500
Micro$oft Natural Keyboard & Logitech Trackball
KVM
sb 5.1 (iirc)
Firewire Card
Sony dual DVDRW


and....

A Partridge in a pear tree

_________________
******************************************
I dont suffer from Insanity - I enjoy it

******************************************

@FuZion

ZERO by universe doesnt work any longer , crisot knows about it (and has know about it since the day we moved away from 16bitPC modes. ).

_________________
See my blog and collection website! . https://www.blog.amigaguru.com

Cheers Toaks,

Both Quake & Earth 2140 are running prefect now. I knew you'd be the one for these

Check, for ZERO. Do you know if he plans to update it? It'd be a shame if the first AmigaOne demo would be the one that also now doesn't work. D'oh!


@Editor

AmigaAMP seems ok here too, with the same skins too. I've not tried that one out quite so intensively though.

FuZion.

Last edited by FuZion on 15-Jun-2005 at 10:26 PM.

@saimo

Thanks for the MysticView tips. I'm sure I have the updated files but I'll check em out.

The YAM thing is an odd one. It feels like, you know when your mouse buttons start playing up & you have to push extra hard? It's like that but it only happens with, YAM 2.4p1 [020]. The left button is fine & even the right button on the e-mails themselves (Context menus etc...)

The "7" key is REALLY weird! Since 3.9 I've experienced it I tells ya. I could REALLY notice it on my classic because it would actually slow the system down, taking up my precious clock cycles. On the A1, I only know about it when I head to a text input thing.

FuZion.

@The_Editor

Quote:

FinalWriter ...............Nothing full stop

FW works for me, no problem. Make sure in UBoot under Integrated Peripherals that PAR Port Mode is set to "ECP". The only other thing that ever makes it not work is FW prefs files. Rename or delete the FW prefs. These two things are always the culprits with FW.

_________________
Amiga user since 1985.

@FuZion

As for YAM, why 020? I guess it's about time to update to the native PPC version

As for the "7" thingie, do you perhaps have any exotic patch/commodity?

saimo

_________________
RETREAM - retro dreams for Amiga, Commodore 64 and PC

@saimo

I wasn't finding the OS4 version very stable. I have the 2.5 Dev version here & it looks nice but it's not quite ready for normal day usage.

The "7" thing happened to me on my classic & has happened here on my A1. Two different computers. I'm gonna guess that it's one of those extremely rare things that can't easily be traced & has been, unwittingly, ported to OS4 too. Maybe

FuZion.

@FuZion

Hmmm.... I've got AmigaAMP here doing the graphical glitch thing that Amplifier has been doing. When I load up my Kenwood skin. I (Although am not an expert) am thinking that this may have something to do with datatypes.

FuZion.

@FuZion

Did you use the same keyboard with your Classic? If so, the "7" bug is definately the keyboard initiation that fails because I sure has never ever seen such a bug (except when my home-made middle mousebutton shorted ;)).

The menues in YAM are annoying and happens with the latest nightly OS4 builds too. But I think this has much to do with the fact the when one reaches for the menu, it is very easy to click the RMB before actually getting to the menu of the screen. And one needs to move the mouse there first, wait one v-blank (or something) for the context menues to be logically replaced by the screens menu, then click the RMB. Try doing it very slowly and it never fails, not for me anyway. Disabling ContextMenus also improves the behaviour because the logic does not need to shift from YAM R-click menues, to ContextMenus' menus and then to the screen menu during the move of the mouse.

AmigaAmp gives gfx garbage when loading different skins here as well, with upd3. It never did with upd2 IIRC. Many different skins garbles the screen, in different ways.

And net usage plus music still eventually hangs the machine with upd3, like I've described in many threads earlier for upd1 and 2

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@FuZion

i guess i know the answers to all of your questions but seriously...im fed up of typing everything a million times... O_o (u know...people ask the very same questions in millions of threads and on several diffrent boards...)

anyway feel free to ask about stuff but dont always expect me to answer...as i have a lot of stuff to do...

regarding zero , well i know what he said and all..now it only matters what all you guys will do to him in emails

_________________
See my blog and collection website! . https://www.blog.amigaguru.com

@Deniil715

Quote:

And net usage plus music still eventually hangs the machine with upd3, like I've described in many threads earlier for upd1 and 2

Have you tried tunenet? I've had crashes with both Aminetradio and Amplifier but TuneNet runs fine.

@Toaks

I can't find the thread about Napalm, so I'll ask here as it seems relevant.

Under Update3, Napalm works as well as it did with Update2 (ie. gets as far as the scrolly Napalm logo and then just sits with a blank screen), except the graphics are now corrupted (presumably endian issues). How did you get Napalm to get further than this?

Chris

_________________
"Miracles we do at once, the impossible takes a little longer" - AJS on Hyperion
Avatar is Tabitha by Eric W Schwartz

@FuZion

Quote:

> Amplifier - Some skins cause graphical glitches on the Workbench screen. Examples of my skins: Good skins = Base, Stella... Bad skins = Sony, Kenwood (Is this a Datatypes based issue?)

Trash in, trash out. Didn't test the skins you've mentioned (don't have them) but some others and from what I see is that Amplifier tries to blit from one bitmap to another with source offsets that don't exist because the source bitmap is too small. Eg. it tries to blit from offset x = 35 but the supplied bitmap is only 16 pixels wide.

_________________
Stephan Rupprecht - AmigaOS4 developer

@The_Editor

PR3 issues:

No problem with Final Writer

I also reported the 'nucleo' skin problem with Amplifyer. Nucleo OK with AmigaAmp. No error message on quitting Amiga Amp though.

Screen Mode utility - causes a lock-up when saving a changed screen. New changed screen size displayed correctly on re-boot

TrevorDick

µA1-C standard

_________________
No, I don't need no reason, I'm just breezin'

@FuZion

The OS4 PPC version is perfect! Be sure to use the lastes nightly build and mcc_texteditor.

_________________
ikir

@Chris_Y

napalm is the bitch.

you need to try all rtgmaster versions u can find (abit like bubble heroes) and once u can get past the scrolling napalm logo then it works except for a few minor glitches (like d-pad keys wont respond) .

best is to dig high and low for old rtg masters and once installed copy over the os4 lib, a big job...i gave up some months back as i wanted other games to work over this one and sadly napalm is one of the few that works with this version of rtgmaster, if memory serves me correct ... it was one from 97 or before. (39.x)...but i am not sure anymore.

closer to os4.0 i will look further again but for now i will not.

ps: the graphics problem is rtgmaster not liking the new 8bit modes on the radeon , on voodoo there is no such problem so the problem is somewhere inside the radeon driver.

_________________
See my blog and collection website! . https://www.blog.amigaguru.com