It is a fact that AmigaKit offers great support, so drop them a line!

@danwood_uk


This is common in Amiga, the solution is infront of you but you got to search carefully.

Here are some Amiga related videos that I have created:

Amikit running on my 4000:
http://www.youtube.com/watch?v=W64MSw8ATN8

Paloma TV Card @ Amiga 4000:
http://www.youtube.com/watch?v=9e58CmRPH-o&feature=channel

Amiga 4000 Triple Boot (description in Greek):
http://www.youtube.com/watch?v=enBgmAOPbAE&feature=channel


Enjoy!

@nubechecorre

Thanks so much man.

I was ready to type "fixed" and I saw your post.

The horizonal and vertical stuff was the missing link and should be set currently on the tooltypes.

Now everything is back into normal mode.

Thanks.

Thanks!

I did it but with no success.

I guess that all the settings of the driver are stored in the PicassoIV.info file.

I bring back the original PicassoIV and PicassoIV.info file from the Stroage folder but still no normal picture -flickering-.

I guess I should edit the correct settings and values on the tool type section of the info file.


Would be great if someone with a PicassoIV card on 4.0 could send me the .info file to use as an example. I got a normal TFT monitor.

Or paste the tooltypes stuff in here/


Thanks.

Amiga 4000 / OS4 Classic -- Is there any way to re configure my PicassoIV modes without re installing the whole OS4? I deleted the PicassoIV driver by mistake, brought it back form the 4.0 CD but not even picture in Monitor after the reboot. Brought the PicassoIV driver from the 3.9 install and the system would boot only in PAL mode.
Any help?

IS athere any fTP Sever software for AmigaOS 4.1

I do not want to connect ton FTP sites but I want to use my SAM as a little FTP server sharing online a part of its hard disk.

So far I have found only FTP clients for AmigaOS 4.1

Any suggestions?

Thanks.

@ChrisH

Thhanks! On my other systems it works fine. OS4 classic is the problem.

No one?

The site would open after I use setenv WEBKIT_IGNORE_SSL_ERRORS 1 on a shell but it would return me bakc on the login page after I enter name and pass. Same would happen on a Greek Amiga site as well. Beside this OWB works fine but I wonder where I can find a 3.14 version to test for the same symptoms.

It would be great if an OS4 classic user post if the same problems with gmail are on his system too.

Would be a solution run the OS4 classic update?

Every time I try to reach Gmail via the latest OWB on OS4 classic of Amiga 4000PPC I take this error message:

Loading http://www.gmail.com/ failed.
peer certificate cannot be authenticated with known CA certificates

I think it worked before. I have played with internet settings to work with the new Poseidon but now everything is set back to normal and I have no other probs with any site.

Any ideas?

Quote:

Did it that way and it worked! Thanks Framiga!!!!

Mine is DH1 by the way. I do not know, the previous file was created on Notepad with same name -BootDevice- and same single DH1 line inside...

Only Amiga God knows...

The message do not appear now. Actually it appeared when I was trying to enter OS4 boot menu to re set the DH1 partition as boot partition. Now that OS4 boots right away, no boot menu, no message. But still if someone has an idea about this message or what it means -see my first post- can post here, just for the record, although I am almost sure it is a compatibility issue of cybppc.device.

Anyway... I am happier now that my OS4 boots right away :)))

Thanks again for all the help and support!!!!

@Framiga

hmmm

I have original OS4 classic. I have not updated yet to the updates provided by Hyperion. Would this update provide me with the correct 51.14 version of Bootloader? In different case how should I find it?

MODULE Kickstart/BootDevice

is added that on kikctsrart layout.

(this line was actually REMed -;- and I simply activated it, adding the BootDevice file in the DH1:Kickstart folder-.


BootDevice text file includes that line only:

DH1


I get error message on boot:

Failed to proload loading Kickstart/BootDevice
Could not proload Module list.


Is it something wrong on the path specification?

Should I add MODULE DH1:Kickstart/BotDevice ?

Or is the error on the syntax of BootDevice file command?

Please give examples.

@pekdar

As soo as I return home will check the specs of my OS4 partition and re post here.
You probably do something wrong with the specification you are giving to the OS4 partition.

Quote:

Ahhh it could be. Although it appears only when I am trying to enter OS4 -and not MorphOS-, but your explanation still makes sence.

No big deal after all cause everything works fine but I just want to know what is behind this message.

As far as Thomas suggestion I already point that I added a text file called BootDevice in Kickstart directory of OS4. The text file contains only the line DH1 which is the boot partition of 4.0. It did not do the trick cause I still need to enter in 4.0 boot menu. Perhaps the syntax or the filename has an error. So if anyone knows something more it would be better to add or correct me.

I will also check the topic on AmigaWorld. It is always interesting to read such kind of info.

@Framiga

ok lets say that I change the boot priority and make the machine start from DH1 and OS4 would that make a difference?

I just want to know what this message is and to avoid entering in OS4 boot menu if it is possible.

Quote:

That would be great. I think the file is called BootDevice and it should be created inside the kickstart directory. It should contain only the boot drive for example DH1. I did this way and it did not work. Any mistakes or any kind of different filename / syntax?

And again I want to know if this message should worries me. I too a look into the manual of CyberStorm but nor reference and I do not know if it was there form the first time I booted into 4.0. If it is an OS / software issue it is really no big deal for me. I just want to know that my CyberStorm PPC does not have any trouble.

Quote:

Boot priority:

DH0 - 3.9 - 3
DH1 - 4.0 - 2
DH2 - MorphOS - 1

Well I want 3.9 first as it is still the OS that works fully in my Amiga. Still got all my WHDLoad stuff in there, have set up my Internet connection and my Paloma TV Card. 4.0 and MorphOS are still in progress. Moreover the Amiga came with 3.9 pre installed and the well known case with the Amiga not recognizing big hard drives was solved, my 60giga drive was recognized fine and well. I do not know if this was due to 3.9 being first but I did not want to destroy its partition.



Quote:

It appears when I try to boot to OS4 after the first early Boot Menu and before the OS4 Early boot menu. I am not switching between any OSes just open the Amiga and go to OS4.

EDIT After switching between OSes check: The message also appears at switching from 3.9 @ 4.0 (soft reset) and from MorphOS to 4.0 (soft reset), but again I have to point that it appears only before 4.0 early boot menu.

Fixed.

A commands order re arrangement on the startup sequence did the trick. The Net interface was loaded before the USB stack and that was the problem.

Chris Hodges replied to my email in MINUTES, giving some extra advice and suggesting me to check the right command and command order in the startup sequence. Well this is real hardware support a big thanks to him (Deneb rules!!!!)

On the 4000PPC my triple boot is created on an 60Giga hard disk. Firts partition DH0 has 3.9, second DH1 has 4.0 and third DH2 has MorphOS. There is a common DH3 storage partition viewable by all OSes.

I use the early boot menu to choose partition, in the case of 4.0 I have to re enter in its own ROM's boot menu to re-set the boot DH1 partition.

Ealry Boot Menu appears by pressing the two mouse buttons on startup.

There are sometimes when I change boot partition to boot on OS4 that during the boot and BEFORE I get into the Early Boot Menu of OS4 to re-set the boot partition, that a window in orange color -text mode- appears with this message:

CS SCSI: No terminators. Not scanning for devices.

After I press the left mouse button the message disappears. I get into the early boot menu of OS4 and everything rolls well.

Have no hard disk problems in any of the installed OSes.

Should I get worried about this message?