Hello, this is my first post to amigans.net, my usual
hangout is amiga.dk which is a lot smaller
and more intimate, so please folks! Be gentle with me
Ok, I don't know for sure whether this is a hardware
or software issue. Actually it might be two separate
issues, or they might be related, I don't know.
My machine: SAM-flex with 512 RAM and Radeon 9250 128 MB.
1) LoadMonDrvs doesn't find the Radeon modes during
the startup-sequence. When I reach the Workbench
screen, only 8-bit PAL modes and one BootVGA mode
are available. I found a "solution" though:
When I open up a shell window and
type in "C:LoadMonDrvs", then go into ScreenMode
again, all the Radeon modes are now available!
I tried booting from the Install CD. Same problem.
I tried inspecting and changing the tooltypes of
the "Radeon" monitor in DEVS:. Nothing changes.
I tried different things with the startup-sequence;
increasing STACK, moving the command to the
beginning and end of the script, inserting 'WAIT 3'
statements all over the place and even inserting
two or more calls to the command in the script...
Nothing changes...
I'm especially puzzled by the fact, that booting
from the AmigaOS CD doesn't change it either.
And moreover: This problem didn't come after
an upgrade or a concious change in the system;
it started about three days after I got the system
directly from ACube. The first three days everything
was normal!
2) DvPlayer now seems to exhibit some problems.
I'm not sure when this changed, as I only tried
the program out one time the first day and then
again last week. It hangs the entire system
when I try fast-forwarding in a movie (I tried
only one DVD). It also hangs the system at
startup when my screenmode has the Autoscroll
tag on.
I talked to Stephen Fellner about it, and he
says that especially the Autoscroll problem in
DvPlayer shouldn't happen unless my screen
has a different size than the selected
resolution (like a larger-than-the-screen
Workbench), which wasn't the case when I
got the hang. I'm posting this here on Stephen's
suggestion.
Does anyone have a similar problem or an idea
of what could be the problem? I'm really affraid that
this might be an obscure hardware problem on my
system. How could I test this?
Before I found
the "solution" of calling LoadMonDrvs after startup
(and it took a LOT of time before I found out,
being kinda stupid and all :) ) I had the system shipped
all the way back to Italy, and ACube just
claimed, that in their hands my system ran
completely flawlessly! I also tried another
Radeon board (same kind), changing the monitor,
same problem...
Help!---