Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
138 user(s) are online (93 user(s) are browsing Forums)

Members: 0
Guests: 138

more...

Headlines

Forum Index


Board index » All Posts (ZeroG)




Re: Installing JXFS
Not too shy to talk
Not too shy to talk


@Deniil

Check if the Last ID, Last TID, and Last LUN buttons are set the right way on all your hdds in MTB.

Go to top


Re: 24" monitors.. 1920x1080 or 1920x1200 ?
Not too shy to talk
Not too shy to talk


@jahc

Quote:

I'll rephrase.. some monitors have DVI, DVI-D, etc, and I dont know what the Sam is compatible with.. my question is: will this monitor that I'm planning on buying display ANY resolution? will it do at least 1280x1024? :) (i.e. is the Sam's DVI monitor port compatible with this monitors DVI port..)

Thanks.
Yes, that will work. The SAM has a DVI-I port that supports DVI-D and DVI-A.

Go to top


Re: 24" monitors.. 1920x1080 or 1920x1200 ?
Not too shy to talk
Not too shy to talk


@jahc
Quote:

well, adding +RB to the screenmode tooltype reduces the bandwidth needed for the resolution..

I have +RB added, without it my monitor don't show anything that is bigger as 1600x1200.

Quote:

but yeah I'm aware that theres a risk I may not be able to use the native resolution!

Ok.

Quote:

my question is.. will ANY picture on that monitor work with Sam?

Sorry, english in not my native language - I dont understand the question.

Quote:

Also, this monitor is 1920x1080, not 1920x1200.... so that may ease things too.

Here even 1600x1200 at 8bit has bandwidth problems on the SAMs M9.

Quote:

Also, I'm aware I'llrun out of video ram a lot faster, I use 16bit modes already though.

Yes, that will happen, at 1920x1200 in 32Bit and hardware compositing on it takes the WB Screen, 2-3 small WB windows and 2 fullscreen Shells and the 64MB are full.

Go to top


Re: 24" monitors.. 1920x1080 or 1920x1200 ?
Not too shy to talk
Not too shy to talk


@jahc

You will probably run in some bandwidth problems with DVI-D (not DVI-A or VGA) if you want to use large resolutions with the onboard M9.

Let me quote from a email i got from ACube:
Quote:

On?the?M9?the?DVI-A?and?the?DVI-D?are?driven?from?two?different onchip?units,?even?if?they?share?the?same?physical?connector.
While?the?DVI-A unit?has?an?higher?bandwidth?to?cope?with?resolutions?up?to?2048x1536?and?higher,?the?DVI-D?has?a?lower?bandwidth.
At?1920x1200@60?you?are?using?the?unit?over?it's?possibilities,?and?has?result?you?see?artifacts.
In?order?to?use?1920x1200?I?suggest?you?to?modify?the?Radeon?icon?tooltype,?starting?from?50?Hz?and?then?going?up?until?you?get?a?stable?picture.


However, my monitor (Eizo FlexScan HD 2441W) don't like anything below 60Hz without a huge "out of range" message in the middle of the picture that won't go away...

Go to top


Re: Strange KB/Mouse Lock Up
Not too shy to talk
Not too shy to talk


@Atheist

Oh, just forget to tell you something:
The 4.0 final update iso is currently not available, i guess that Rogue simply forgot to put it back online after the last server crash at hyperion. You may want to write him an email.

Go to top


Re: Strange KB/Mouse Lock Up
Not too shy to talk
Not too shy to talk


@Atheist

But OS4.0 Final and the July update are free for A1-early birds. You simply need to register at hyperion and can download it. You only have to pay for OS4.1.

Go to top


Re: Strange KB/Mouse Lock Up
Not too shy to talk
Not too shy to talk


@Atheist
Quote:

I'm using AOS4 prerelease 4

Why are you still use a OS4.0 betaversion and not Final + July update?

Go to top


Re: Picasso96Mode/Screenmode on OS4.1
Not too shy to talk
Not too shy to talk


@RuDeE

Read SYS:Documentation/Picasso96/ScreenModes.doc
Set HSYNCMIX/MAX,VSYNCMIN/MAX for your monitor, and add the line
1920x1080@60+RB
You may want to change the 60 to something you monitor manual says.

Go to top


Re: OS4.0 system hangs on boot after OS4.1 SDK install
Not too shy to talk
Not too shy to talk


@cha05e90

SOBJS: are supported in OS4.0 (with the newest updates), but cairo is OS4.1 only.

Go to top


Re: Installing new SDK
Not too shy to talk
Not too shy to talk


@xenic

You can extract the complete SDK and compare the md5sums of all so's.

I have found this "new" so's in the SDK:
Quote:

1.RAM Disk:test> md5sum "" ALL
2ae9ea81e507bcad6c8181a5c83aecdc libc.so
03b476600c2e54b50d890aa73ca134f7 libpthread.so
3de694e73ce5068bf96c337967dd6030 libstdc++.so
6eb5d7cdb690b6d2453da0fb5a8ae0d1 libssp.so
25e9d30e612c63aaaf45d9cf210f1ddf libgcc.so

Go to top


Re: OS4.0 system hangs on boot after OS4.1 SDK install
Not too shy to talk
Not too shy to talk


Check that the new shared objects are in SOBJS:
Quote:

1.RAM Disk:test> md5sum "" ALL
2ae9ea81e507bcad6c8181a5c83aecdc libc.so
03b476600c2e54b50d890aa73ca134f7 libpthread.so
3de694e73ce5068bf96c337967dd6030 libstdc++.so
6eb5d7cdb690b6d2453da0fb5a8ae0d1 libssp.so
25e9d30e612c63aaaf45d9cf210f1ddf libgcc.so


Edited by ZeroG on 2009/8/24 17:55:33
Go to top


Re: Sam Flex and SoundBlaster cards?
Not too shy to talk
Not too shy to talk


@328gts

no, just visit SYS:Prefs/AHI.

Go to top


Re: usbprinter.device "error 4"
Not too shy to talk
Not too shy to talk


@tonyw
Quote:

But you're not using printer.device or a1parallel.device, you're using usbprinter.device. I don't understand why you need a "USBPAR:".

That was only a test to see where the error comes from.

I think that this thread is of use:
http://amigaworld.net/modules/newbb/v ... p?topic_id=28423&forum=14

The "guy over here in germany" is getting the same error 4 message from usbprinter.device.

BTW: It would be nice if "USBRAW:" could be autocreated/mounted by the usbprinter.device.
It's a very usefull counterpart to the printtofile.device.

Go to top


Re: usbprinter.device "error 4"
Not too shy to talk
Not too shy to talk


@tonyw

The other way around: USB->Parallel->Printer.

Go to top


Re: TuneNet Testing (V86.66)
Not too shy to talk
Not too shy to talk


@bean
Quote:

Many Thanks, I've now fixed this in the latest internal version (V0.90). Thanks for the good bug report at OS4 depot.

If that was a good bug report, i don't want to see a bad bug report...

Thanks for fixing this.

I dont know if this is a bug report or a feature request but the SkinFX GUI does not respect the "Screen edges resistance" setting in Prefs/GUI for Off-Screen window dragging. It would be nice if TN would do that.

The same is true for the [CTRL] + any [Alt] shortcut for resizing windows from all sides/corners.

Go to top


Re: TuneNet Testing (V86.66)
Not too shy to talk
Not too shy to talk



Go to top


Re: 24" monitors.. 1920x1080 or 1920x1200 ?
Not too shy to talk
Not too shy to talk


@Deniil
Quote:

I would go for the slightly more squared 16:10 monitor unless you are going to feed it 1080 Full-HD material which obviously looks better on a true 16:9 display with 100% pixel-to-pixel matching.


Most likely there is an option in the monitor to disable scaling for input from the hdmi-port. My 1920x1200 monitor dont even let me enable scaling for 1080p signals over hdmi.

Go to top


Re: Installing JXFS
Not too shy to talk
Not too shy to talk


The FFS2 readme in SYS:Documentation says:
Quote:

...
3.2.6 Size limitations

The smallest unit the file system can access is the sector, as
provided by the underlying device driver. Up to 2^32 sectors can be
used, which with a sector size of 512 bytes yields a maximum partition
size of about 2.2 Terabytes
.
...

Go to top


Re: 24" monitors.. 1920x1080 or 1920x1200 ?
Not too shy to talk
Not too shy to talk


@jahc

both modes are over the spec of the onboard DVI-D on the SAM, and for both i get "out of range"-errors from my monitor. VGA (DVI-A) is working in both modes, but the picture quality is bad.

Go to top


Re: AmigaDos
Not too shy to talk
Not too shy to talk


@ChrisH

Sometimes it was installed during the development of 4.0 sometimes not - but it was always on the CD/ISO.

Go to top



TopTop
« 1 ... 4 5 6 (7) 8 9 10 ... 20 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project