@MattBullock
Quote:

2.) Voyager 3.3beta126 has a strange issue with images - it only shows the left third properly, the rest is grey. This happens with all jpgs and gifs; the png images I tried display fine.

MysticView has the same problem. Only displays the left third of the image properly. In addition the control gagdgets at the top of the window aren't rendered properly.

Bummer! This was my favorite picture viewer.

Other than that, so far Update 3 is great! Install went very smoothly. I read the directions first. :)

_________________
Kevin - X1000 First Contact / A1222+

@ssolie

Well, good to know that it's not a bug

However, may I ask why?
I think that it's a change for worse, as here now both files and dirs have the same colour. I understand that this may be just because in my own color settings two pens have the same color, but then it's not that easy to change pens without affecting the rest of the GUI...


saimo

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

@ktadd

MysticView works like a charm here. Make sure that you have the latest stuff from the Binary Distillery and, most importantly, the AOS4 versions of the guigfx.library and render.library (available on Aminet).


saimo

Last edited by saimo on 15-Jun-2005 at 07:08 PM.

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

@saimo
Quote:

However, may I ask why?

No you may not. I bid good day to you sir.

Let's just say you can't please everyone. At least with the new pen I don't see dark blue text on a black background when I'm saving files now. It's a long story and I was one of the guys pushing for the change so go ahead and blame me.

_________________
ExecSG Team Lead

@saimo
Quote:

MysticView works like a charm here. Make sure that you have the latest stuff from the Binary Distillery and, most importantly, the AOS4 versions of the guigfx.library and render.library (available on Aminet). saimo

Thanks, glad to hear it is working for someone. That give me hope. I know I'm using the AOS4 versions of the libraries and I think I'm using the proper version of MysticView but I'll have to check for sure when I get home. What versions of the Libraries are you using?

_________________
Kevin - X1000 First Contact / A1222+

@Orgin

Here's a Problem for your list:

AmigaAmp 2.14 crashing with update#3, didn't l ook further into it...

More important is, that Chris_Y, the MAN, has found an workaround to the
most annoying Radeon9800-bug:

After installing Update#3 and following the steps described in the PDF, simply
copy over the ATIRadeon.chip from the last update to your Sys:Kickstart/
drawer and it will work again (Well, at least for me - Radeon9800 - it has!)

On this way, thanks goes out to Chris_Y...
or maybe better a

Last edited by Raziel on 15-Jun-2005 at 07:32 PM.

@Orgin

I must say I didn't manage to get the system to work with the instructions mentioned, ie hang with an empty "Workbench" screen.
I booted with Update1 CD and tried to fiddle with P96mode & Screenmode prefs but it would hang until I replaced the devs:monitors/Radeon with the previous version in my backup partition. Now works as usual but of course missing the new features of the monitor driver (if any). Having a Radeon 7000.

Marko

@Raziel

Please, I'd rather you didn't kiss me (unless you're female, which I suspect you're not)

That was a good temporary workaround, but try disabling the INTERRUPT=YES tooltype in DEVS:Monitors/Radeon first, as you can't use Warp3D stuff with the old driver.

@thread
How do you use the usbprinter.device? I figured it would just be a case of plugging it into printer prefs, but that doesn't seem to work.

Also, my USB keyboard disappears on most boots. I think I've cured it by replacing hid.usbfd with the old one, but this seems to be a bug. I guess I'm not missing anything important by not using the new HID class, as no additional HID devices are supported. If anybody has a better solution for this problem, though, I'm already listening.

Chris

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

Hello all,

well, here is another Problem with ArtEffect4

load a Picture and resize with + or -
the Picture is always garbled
originalsize is ok.

@ktadd

I'm running MysticView alongside Voyager right now and it's running fine (MV, that is - V's still dodgy - although I just had a funky instance of the corrupted part of an animated gif in Voyager showing a scaled down picture displaying in MysticView!).

Versions - MysticView 1.05; mysticview.library 4.1; guigfx.library 20.0 (OS4); render.library 40.8 (OS4);


Matt

@Raziel

Quote:

Raziel wrote: @Orgin Here's a Problem for your list: AmigaAmp 2.14 crashing with update#3, didn't l ook further into it... More important is, that Chris_Y, the MAN, has found an workaround to the most annoying Radeon9800-bug: After installing Update#3 and following the steps described in the PDF, simply copy over the ATIRadeon.chip from the last update to your Sys:Kickstart/ drawer and it will work again (Well, at least for me - Radeon9800 - it has!)

And presumably not overwriting kicklayout then as well?

_________________
Are we not done with the same silly arguments and flames yet??!

i found the following problems so far:

1. maxon cinema renderer now crahes with a grim reaper. ignoring it continues but it hangs soon after (using "glasbuchstaben", defult settings, rendering on cinemas screen) - it worked before - with wrong colors but withour a crash.

2. when mounting e.g. DVDMRW (or any other DVD*/CD*) i get a grim reaper (and yes, the device is correct). i already got this with update2. using an older smartfilesystem (the original one from the prerelease) helped then. i did not try it yet. also formatting a hard disk gave me a grim reaper with upd2 - did not check it yet.

3. the gui prefs settings don't seem to work any more. i had a special setting for the ibrowse screen (os4 aqua style). now it switches to the "classic" look when opening ibrowse - not even the normal os4 look.

4. if i try to load a gui prefs file on workbench i get the "please close all windows..." requester. but nothing is open. actually the same is open like when i used it with update2 - there it worked...

any suggestions?

thanks and
byebye...

_________________
Michael Merkel
(Michael.Merkel@gmx.net Home)
Member of Amiga-Freunde Pfalz, OS4 Welt

@ssolie

Quote:

No you may not. I bid good day to you sir. Let's just say you can't please everyone. At least with the new pen I don't see dark blue text on a black background when I'm saving files now. It's a long story and I was one of the guys pushing for the change so go ahead and blame me.

I understand.
I did not have that problem because my highlight text (I guess that's the pen used, right?) was (and is) a nice red.
No, I won't blame you nor push for a rollback, as I'd say that the best thing would be making it customizeable.

This leads to a suggestion I already had in mind to make to Massimo Tantignone: I think that for each element of the GUI (that allows pen configuration), it should be possible to assign _any_ pen, not just a subset of those available (f.ex. the scrollers pen can only be either "fill" or "foreground") - the current solution is not very flexible.
Probably the only problem is creating a general-purpose pen chooser, and I hope that it's just a matter of time before it arrives


saimo

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

@MattBullock & ktadd

Quote:

Versions - MysticView 1.05; mysticview.library 4.1; guigfx.library 20.0 (OS4); render.library 40.8 (OS4)

There are newer versions of MysticView (1.07) and its library (5.0) available at the Binary Distillery repository (link posted above).


saimo

Last edited by saimo on 15-Jun-2005 at 08:01 PM.

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

@Chris_Y

OK

No kisses for you then

To the Interrupt, it won't work for me, because as soon as there is some display
opened it crashes, i just tried, commenting it out and using the Upd#3 .chip,
but it still crashes, so i have to live with that, for now

@saimo

Quote:

saimo wrote: There are newer versions of MysticView (1.07) and its library (5.0) available at the Binary Distillery repository (link posted above).

Thanks. Doesn't look like there's much difference, but I've installed them anyway and they seem to work fine.


Matt

@Orgin

I have to take back the AmigaAmp crashing, for now.

It seems ALL of the programs which use sound or play music crashing on my system
and YES, i have the latest AHI installed, it's rather i'm on a beta SoundCard
driver which causes it, so please take out AmigaAmp for now, starting fine here,
just crash when playing music

Sorry for the inconvenience

@blmara

Answering to myself. I managed to get the new Radeon driver working by changing it's tooltypes to "Interrupt=No" as somebody adviced in another thread. No idea what it actually does, is the interrupt thing important?

Marko

@blmara

Sounds like it's going to make the system take a preformance hit, but that's it.

----------------------------------------------------------------------------------------------

Interrupt
From Wikipedia, the free encyclopedia.

In computer science, an interrupt is a signal from a device which typically results in a context switch: that is, the processor sets aside what it's doing and does something else.

Digital computers usually provide a way to start software routines in response to asynchronous electronic events. These events are signaled to the processor via interrupt requests (IRQ). The processor and interrupt code make a context switch into a specifically written piece of software to handle the interrupt. This software is called the interrupt service routine, or interrupt handler. The addresses of these handlers are termed interrupt vectors and are generally stored in a table in RAM, allowing them to be modified if required.

Interrupts were originated to avoid wasting the computer's valuable time in software loops (called polling loops) waiting for electronic events. Instead, the computer was able to do other useful work while the event was pending. The interrupt would signal the computer when the event occurred, allowing efficient accommodation for slow mechanical devices.

Interrupts allow modern computers to respond promptly to electronic events, while other work is being performed. Computer architectures also provide instructions to permit processes to initiate software interrupts or traps. These can be used, for instance, to implement co-operative multitasking.

A well-designed interrupt mechanism arranges the design of the computer bus, software and interrupting device so that if some single part of the interrupt sequence fails, the interrupt restarts and runs to completion. Usually there is an electronic request, an electronic response, and a software operation to turn off the device's interrupt, to prevent another request.

@blmara

What are your interrupt settings in u-boot?

Open u-boot prefs in Sys:Prefs and under hardware check to see if you have all interrrupts set to trigger level and A,B,C,D set to 9,10,11,7 respectively.

No idea if this could have anythig to do with your problem but it was a thought.

_________________
Fixed A1G4XE 7455 RX933PC with fried CPU
Sapphire Radeon 9100 128mb
ESI Juli@ 24bit 192kHz Envy24HT
Sil 680 Ultra Ata 133 E-ide
SeaGate Barracuda 120gb 8mb cache