I'd say you're pretty lucky to be able to boot with a Mediator attached (guess it doesn't cause pbs when unused ;) It's really hard to say what's the reason of your pbs. It may be faulty memory, but could be something else as well. You could try dumping the logs after a crash on 256meg, this might help us indentify the issue.

Well... this log looks like a working boot to me ;)

The Ambient's reboot/shutdown feature is prolly bugged - blame the gpl coders :)

The command is correct if you run it in the supplied startup-sequence. Otherwise it's broken. Check your AmigaOS manuals for the meaning of $ in scripts.

Hi,
is there a commande to add to limit the "boot" memory to 128mb ?
because I would like to replug my other 128mb of ram..
It remind me the "mem=254m" when you want to install a linux on a Pegasos 1

nah ..I'am again..but now MOS works :) BU still have problem...first..I don't have sound?Why? Dont know..How I can change screenmode to 1024*768? In menu I have 800*600 max..don't know why..And opening window its slow..how I can speedUp this? and all other works OK for now :)..

@jacadcaps

I guess i'm lucky indeed

Regarding my memory problem, seems that is not a faulty memory. If i exchange the two modules, both works well if only one of them is used at the same time. And my AOS 3.9 install works flawlessly with both modules attached, and i have tested them in it's full capacity.

Another thing that gives me indication that it's not a faulty memory problem, is that our friend reported the same problem with his system when 256MB RAM is used.

I would promptly provide you with the debug log when i'm using the two memory modules, but it's already here in this topic. Our friend reported this early, and my log is identical to the one posted here.

By the way, there's no error messages, or "crashs" (i think). The system simply hangs. After the boot caused by the startup command, the screen goes black, the power led dimes and gets full bright again, and you'll be waiting forever for the Cybergraphics logo screen.

I would like to thank you very much jacadcaps, for your patience and continued help in our problems.

Regards,
Marcelo.

@ VooDoo

To change the screenmode to 1024x768, you need to edit the CGX configuration.

In the system settings (click on the desktop with the left mouse button, then click with the right mouse button, and choose settings -> System settings) Select "ModeEdit", and edit the monitor specification.

The default setting is for a generic 31KHz monitor, and it's very probably that your monitor is capable of showing higher resolutions than the one in the standard configuration.

You need to adjust the pixel clock setting, and the vertical and horizontal frequencies as well.

BUT BE WARNED !!!!!

You MUST refer to your monitor manual, in order to get the right parameters. If you decide to try it for yourself, you can damage your monitor for good !!

After changing these settings (remember to save them), you must reboot MOS in order to activate your new settings.

Now you will be able to select a 1024x768 mode, and you can tweak the mode settings as well, to get the best picture.

The configuration program is IMHO the weakest feature of CGX systems. I like the P96 one better.

Regards,
Marcelo.

Vodood: for the slow opening windows, it's a font problem, check the recent posts.

Hi,
I have also noticed a problem with my GREX+Vd3 (I had the same with my Peg1 +Vd5 but not all with a Radeon).

Natively, MOS 1.4.5 is setted to use a 800x600 on a 31.5KHz Monitor. The only way to get this resolution is to set it at 50 Hz ! a 31.5 Khz is "normally" made to be used at 640x480 in 60 Hz.

Now, a lot of modern monitors can't handle this, so they stay black.

People should try first with P96 or CGX if their monitor can handle 50 Hz.

With my peg and a Radeon, it starts directly in 800x600-60Hz.
Take care of that too !

@jacadcaps:

yesterday I made some tests on a friend's A4000D with GREX. The result was the following:

-MorphOS doesn't like the motherboard's 16MB (not a problem, 128MB on the CSPCC will be enough; and after thinking about it, I remember reading that MOS limit was 128MB)

-If you leave the fakerom.elf and put set $kickstart "nokickstart". It won't show the MOS logo and won't try to boot. If you take out the fakerom.elf file it seems that it tries to boot.

-If you tke out fakerom.elf and put kickstart erm... xx.70 in Devs and put the path in the SS, it tries to boot and shows you the butterfly logo but stops there.


I think that the problem is that MorphOS doesn't recognices the partition even forcing MOS in the SS to use it.

We tried to boot with a AmigaOS3.1 floppy disk and we formatted the partition with that old FFS, but I guess that it would have been even better to also change the FFS from 3.1 HDToolbox. We tried to force HDtoolbox from WB3.9 to use an older FFS and it seems that the partition used it. My friend has done that in other situations to be able to load old Zip cartridges formatted with an older FFS so that should work...

Would it boot if we changed the partition to use SFS? That would require seting a partition to boot the kernel and another one for the MorphOS system formatted with SFS, wouldn't it?

Any ideas? We have removed every zorro and PCI card but the Voodoo3. But it still stops when it shows the MorphOS butterfly logo.

Once we make it boot we'll let you know...

[ Edited by Crumb on 2005/9/9 13:37 ]

Trying SFS surely is a good idea and no, you won't need separate partitions. Just make sure to put 68k SFS into RDB.

Hello CLS2086

its a typo or?

bootdevice=MOS

MUST be

bootdevice=MOS:

Hi Framiga,
i took the easier way, I name the partition DH0 and leave the starup sequence untouched (DH0), and so it works.

not here with CSPPC (AFAIK BlizzardPPC acts different).

The only way to get MOS boot always (as already said), is to use
device name for the boot partition (only if you don't have MOS as
highest bootpri)

Hence

set bootdevice "bootdevice=CDH0:"

having the MOS boot partition i.e

System3.9 (a spare boot partition of mine) as partition-name and CDH0:
as device-name.

If you have the highest bootpri, this option is ignored.

EDIT- have you managed, to improve the "jercky" mouse pointer in some
way?



[ Edited by Framiga on 2005/9/25 17:30 ]

Framiga its strange to see you posting here after all the flack you gave me on other sites. Well Welcome to MorphOS and enjoy your time here as well.

i'm here to teach something to you . . . wheres the problem?

Hi,
yesterday i tried to find a command to reduce the memory size (I need 256 mb for games, and I don't want anymore to take off the ram each time I switch to MOS).
I found that Comm port was configured to 115kb (impossible to handle for our old classic), and there is well the possibilty to set it at 9600.

start with no boot sequence
cd boot
startup /? or startup ?
(do a CTRL C to make a pause to reed all the parameters).

Is there any docs about these paramaters ?

Thanks,
Chris - CLS2086