I just thought about something..

Have you set the volume in TuneNet above 100%?
Will not work on CMI8738 on ?A1-C.
I get alot of crackles if I raise above 100%.

@Origin

Yes, I agree with those above. OS4Depot is a great place.

Although I have a simple request.. Please give the site a useful search function.

I want to be able to search author, date ranges and maybe some more options.

The 040 is a VERY hot chip. Even 060/50MHz is cooler running.

So it could very well be a heat issue.

@LyleHaze

You have the current ahi.device & CMI driver anyway.
Have you checked AHI prefs?

I have the very same programs, except FKey, in my WBStartup. Plus a couple of more.

Do you run the Mixer in WBStartup or in startup-sequence?
I have mine in WBstartup.

@SpotUp

I have LimpidClock installed and Lyle and me have the same hardware so it can't be that.

You're right though that it could be some other software.
But usually it's a AHI or audio card driver issue. Or he might be using old versions of some software which may cause problems with sound somehow?!

@LyleHaze

I use IBrowse, not AWeb. I wouldn't know how AWeb reacts at all. All I know is IBrowse, TuneNet & AmigaAMP works fine without dropouts on my ?A1-C with Update 4.

I have CMI8738 5.16 driver installed. You same?
Check that everything is correctly installed and set up, especially AHI in this case.
Btw do you have the latest AHI?

@Fransexy

I was talking about having OS4 on a Cell computer.
Generally OS4 has everything that is *required* for it to work as desktop OS. Although some additional features wouldn't hurt Yes, a better Workbench is one of those features.
What's really lacking is applications.

Quote:

Your lid (armour head piece) is closed? Thus you can't see all the nice releases for OS4..

Ahh dial-up.. That sucks!

I had dial-up about five years ago. I remember how slow it was and all the troubles with drop-outs one had.
Broadband is a gods send.

Seriously, isn't it faster and easier to just buy a cheap PCMCIA network card and connect it directly to the router? For the A1200 I mean..
The same goes for the A4000, a second hand network card should be quite cheap.

I know it is not helping your question, which I'm sorry for. I have never tried your approach.

Personally I would buy an external router, which usually has 4 inputs, and connect each computer directly to the router. It's way way easier than your approach. The price of such a router should be less than 100$.
This worked straight away when I tried MiamiDX on my A4000. Just set it up to use DHCP and your online
Routers do help alot with making configuration easier when going online.

@IonMane

Aren't we a wee bit ahead in time now?

OS4(.0) will probably (almost certainly) not be released for any cell platform. 4.1 (or 4.2) might be though. But we are probably talking atleast 3 years in the future probably even more with the current "manpower hours/per day" the OS4 project has.
There's so much more that has to be added or changed in the OS for that to be realistic for now.

@LyleHaze

Do as Raziel adviced and also check that you have the very latest CMI driver installed.
DaveAE did alot of testing and fixing of bugs in the hardware with the latest versions.
With the latest version I can surf, listen to music and do other things without interrups in the sound. That was not possible with the earlier versions of the driver.

http://os4depot.net/index.php?functio ... =driver/audio/cmi8738.lha

@SKOLMAN_MWS

IMO that's not Hyperion's business. Elbox should make OS4 drivers for their stuff when OS4 is released.

Hyperions business is to make OS4 work on classics with BPPC, CSPPC and a couple of the most used gfx cards.
Gfx cards are the most trouble because not many (any?) of the companies are still active in the Amiga market.

@tonyw

Thanks for your input.

The problem was that I just got a black screen when I booted after changing the tooltypes and connected my new LCD. And when I created new modes I got alot of "out of range" messages from my monitor on modes known to work. Now all those modes work "magically".

I think OS4 should revert to a standard resolution known to work on any monitor if the displaylist IDs doesn't correspond to the saved prefs. That's all.

@hnl_dk

The parameters after resolution are for color modes.

e.g. 8bit, 16bit or 32bit.
If you enter MODE=800x600@60 you will get a 800x600 resolution at 60Hz refresh with all three color modes selectable. I usually just need a 32bit mode so I remove the rest with MODE=800x600x32@60. As you saw you may enter two modes aswell separated by a comma.

Hopefully we'll have to wait less than a year for 3.0..

I really want a CSS capable Amiga browser, a real Amiga browser... Not a bloated +10MB one.

IBrowse has the greatest UI other than Firefox 2.0 which has surpassed IBrowse IMO with the latest version. Any improvements in 2.4 and maybe 3.0 can only be for good.

Hi Sundown!

I have everything working now since a couple of days.


Although I tried everything everyone suggested I couldn't get it to work before I edited a mode in Picasso96Mode first. And ofter that remove the Picasso96 settings file. It's really strange. Now everything works as expected. I can add or remove modes as I like, no problems.


@salass00

Oh.. I didn't know that. I just changed alll modes in the tooltypes and even removed some. I guess that's why I got in trouble then.
Still OS4 should revert to 800x600@60 when the resolutions in the tooltypes don't correspond not just don't show anything. Better still, use the standard that exist for getting info from the monitor about its specs (don't remember what it's called though) and then choose an appropriate resolution.

I have now gotten OS4 to boot with a 1280x1024 screenmode.

But there must be a bug somewhere because how I did it is not a normal way (I hope)..

Why does Radeon monitor use Picasso96Settings file even
if I have it removed from the tooltypes?
Why doesn't OS4 open up a 800x600 screen mode when I
have explicitly saved this mode with ScreenMode prefs?

What I did was boot the OS4 update 4 CD.
Open Picssso96Mode prefs program.
Edit the 1280x1024 mode so that it worked and fit.
Saved Picasso96Settings to DEVS:.
Did NOT call Picasso96Settings from Radeon tooltype.
Added three modes (800x600, 1024x768 & 1280x1024) to
Radeon monitor tooltype.
Opened Screenmode prefs (while being in 800x600 from the
CD boot). Saved the 800x600 screenmode settings to ENVARC: of my harddisk.
Rebooted.
OS4 works for the first time in 2 months (since I got the new
LCD) for me. But strangely it opens in the fixed 1280x1024
mode I just had made with Picasso96Mode..

What more strange is that once I saved Screenmode prefs
into one of the modes in the Radeon icon everything works
as expected. Now any new mode works directly.

It can't be expected to have this much trouble just from
changing monitor from CRT to LCD?!?
The problem I had was because my CRT prefs was saved
at 1280x960@85, this is not supported by the LCD so I got
a black screen. It doesn't help just to fix the Radeon icon
apparently.. It seems when screenmode.prefs settings can't
be found it chooses one mode in Picasso96Settings.
I thought OS4 would just revert to 800x600@60 when it
can't find a correct setting for the monitor.

Btw I failed to mention that I had everything working with
a CRT monitor, no problem at all. Even with adding modes.

I have ATIRadeon.chip 51.13

VSYNCMIN=60
VSYNCMAX=75
HSYNCMIN=30000
HSYNCMAX=80000

My LCD actually supports wider specs, 50-85 & 24000-82000
but that makes no difference. Seems the frequence output by
OS4 is not compatible with my monitor

As I said, not even PicassoMode96 won't open a screenmode
I have created even though it's inside specs, without changing
the frame size.

I also have

Boardtype=Radeon
Cmplength=6
Interrupt=Yes
Mode=800x600x16,32@60
Mode=1024x768x16,32@60
Mode=1280x1024x16,32@60 <- Native recommended resolution.

I done this aswell.. Wasn't going to post about it but seems everyone else is so..