@my_pc_is_amiga

Quote:

Based on threads, there seems to be something wrong with those 2 fs_plugn#? files...but the one obvious thing that I haven't heard is why "version" should crash...instead of crashing it should give an error instead...i.e. the old OS3.9 version command works fine...no guru!

It is not the Version command which crashes, it is elf.library. OS3 has no elf.library
and is unable to load ELF binaries, ergo it cant crash on loading broken ELF binaries.
And it is not only elf.library which crashes, the objdump tool (from the gcc binutils)
crashes too, probably the broken binaries contain something like a recursion in the
ELF headers/tables.

@Spirantho

Quote:

Spirantho wrote: @tonyw Thanks for the response - it makes sense. However, I think if that's the case then the "free memory" amount should be removed completely. I'd rather not have a readout at all than one which at best was inaccurate

The contents of the WB title bar can be edited with the Workbench prefs editor.
It was inaccurate in previous AmigaOS versions too, which did not cache free
memory but already cached closed libraries/devices/fonts/catalogs etc.
To get a more accurate estimate of free memory, you can do the same as in OS3:

Add " -DEBUG" to the LoadWB call in the Startup-Sequence, then WB has an
additional "Debug" menu with a "flushlibs" menu item which does something
equivalent to calling "Avail FLUSH", and after this call the reported free memory
is more accurate (until something frees memory again).

Quote:

and at worst completely meaningless (e.g. negative memory amounts).

This is known and should be fixed, it seems it only happens on OS4Classic
so it may be related to the special handling of ChipRAM.

Quote:

Given that the OS is in control of all memory allocation and de-allocation, though, would it not be possible just to keep a tally of how much is allocated? You know exactly how many bytes you start out with, and you know exactly how many bytes are allocated with each call to alloc() (or the equivalent). Therefore at any given time the OS should know from its own internal counter how much memory is available to the system. Even with a garbage collection system the internal calls should still use free() so the memory readout could be accurate. What this wouldn't do, of course, is guarantee that an allocation of a certain size would work, because of the nature of fragmented memory - although this should be somewhat lessened if not eliminated with the new memory system.

There exists a MEMF_LARGEST flag for AvailMem(). The value returned by AvailMem()
is inaccurate since decades because it does not include cached objects which are
freed on demand.

Quote:

When we have working virtual memory, though, we can probably do without the free memory reporting altogether.

You can use the Workbench prefs editor to configure what is reported. IIRC its possible
to report free ChipRAM, free executable memory, free virtual memory, free gfx board
memory etc.

@TetiSoft

"Add " -DEBUG" to the LoadWB call in the Startup-Sequence, then WB has an
additional "Debug" menu with a "flushlibs" menu item which does something
equivalent to calling "Avail FLUSH", and after this call the reported free memory
is more accurate (until something frees memory again)."

sweet, thanks!

Sorry for the maybe obvious question but... where are the docs on how to prep a CDMRW: (for example)?

Is a unique futeaure on AmigaOS4 but i can't find any docs on the CD (got it working after some browsing in the System drawer ... doh! FormatCDRW was what i was looking for!)

_________________

@Framiga

Well, not every new feature is documented in all details.
And IMHO its not necessary to do that.
The user is expected to notice that a new program exists in SYS:System/
and the name explains its purpose and its GUI is simple enough to not need
any extra documentation. There exists Documentation/Kickstart/CDFileSystem.doc
which mentions that UDF is now supported.

@TetiSoft

Quote:

There exists Documentation/Kickstart/CDFileSystem.doc which mentions that UDF is now supported.

Is that a new feature of OS4 Classic?
In the last A1 version CDMRW:, DVD-RW:, DVD+RW: and CDRW: are limited to use SFS as filesystem.

@Framiga

OK, I`ve set it to Sync, but through 3.9 ! Trying to run the RDBFlags on OS4, I got an "error 0 while writing RDB"...
Now I don`t see the reminder that the HD is not set correctly on the Media Toolbox, but the whole disk (all the partitions/volumes) is still read only!

_________________
Ordell Robbie: Is she dead, yes or no?
Louis: Pretty much.

@stevieu

I get the same Preferences error that you got.
DId you get any further with this or is your PPC Card still broken?
Can the loose component not be replaced/resoldered?

Frans

@Cameraman

That's nice to know...in a good way haha. I had no joy in finding out why it kept failing... I hadn't changed my hardware configuration, nor did I install on an existing version of AmigaOS. I formatted each partition from scratch, but to no avail.

My PPC card is in working order, it's my BVision that's broken. Two capacitors/resistors need replacing, so I'm sure it *can* be fixed if I know their values, or send it to be repaired (which I don't really have the money for right now).

I don't really fancy sticking my Voodoo and Mediator back in... I was hoping to just get a working BVision setup.

(back)
Image 1

(front)
Image 2

I'm assuming they're resistors?

Steve


Changed images to hyperlinks /tomazkid
Images in threads: Images embedded in threads should be no wider than 640 pixels, larger images should be hyperlinked.

Last edited by tomazkid on 05-Jan-2008 at 01:35 AM.
Last edited by stevieu on 03-Jan-2008 at 11:58 PM.

_________________
A1200T - OS4.0,OS3.9: 603e PPC 200mhz,060 50mhz, 256mb ram, FastATA MK-III, BVision, 160gb,20gb HDDs

A1200 - OS3.1: Blizzard IV 030, 64mb ram, 400mb HDD

OS4.x - Flying the AMIGA flag

@stevieu

From my experience black ones are resistors,
so it might be some thing else like diode or capacitor.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

Hi,

I sucessfully installed OS4 Classic on my A1200T Blizzard PPC Mediator system.
I had the same issues of my voodoo card not showing up in the Screenmode Prefs.
Firstly I made some screen modes in Picasso96Mode then I copied the Voodoo driver from the OS4 CD (Storage/Monitors), replacing the one in Devs:Monitors on the Amiga OS 4 partition. After a reboot, the voodoo screen modes show up in the Screenmode prefs. I hope this helps.

Drewlio77

@Cass

"OK, I`ve set it to Sync, but through 3.9 ! Trying to run the RDBFlags on OS4, I got an "error 0 while writing RDB"..."

you have a problem indeed!

as i said, you have to fix the HD issue before tweaking with RDBFlags

The errors you get and the sync flags, are 2 different things.

IMHO (and re-reading your first post) the issue is related to your previous attempt to install BSD. What filesystem are you using? and have you used in the past HDInstalTools to prep that disk?

_________________

@Drewlio77

I tried this but no board is shown to attach to.
What version of the Mediator do you use?

_________________
If your nose runs and your feet smell, you're upside down.

Here comes my report about my OS4 Classic Installation.

Configuration :
- Amiga 1200 Escom desktop
- BlizzardPPC (060@50MHz, Ppc 603@175Mhz)
- BVisionPPC
- 256Mb EDO
- an IDE2CF converter populated with a 1Gb compact flash card set as two 500mb partitions.

Installation :
The first problem occured when I had to chose between setting a CD-ROM or my CF-Harddisk in the Amiga. As it is the desktop vanilla 1200, I can only set one of them on the naked internal IDE port, which leaves me with the choice between the Installation CD or the harddisk were the OS will be installed.

The solution came thanks to WinUAE : I mounted the compact flash card (CF) as a new harddisk for WinUAE, ran the emulation, copied the CD files on the Work partition (DH1), and a minimal OS3 system on DH0 to boot it. Then I'll replaced the CF inside the Amiga and booted on DH0. There I'll ran in a shell the "start_from_os3.x" script", and entered the bootmenu after the reset to force the 1200 booting on DH1 (the CD). It booted well, I formated DH0 with long names settings, and ran well through the installation process.

Then I turned of the 1200 during 30 seconds and turned it on again. Caramba! Problem. The 1200 went on an infinite loop of reboots. Strange, as booting from the "CD" worked well.

I set the CF inside WinUAE again and studied my OS4 startup sequence and the CD's one. As I suspected, the Bootloader lines differed. I added the "AllowBasepageAccess" command line and this time OS4 booted with no problems. So amigans with the same configuration than mine may want to check this option when it appears during the installation procedures (I unchecked it during the process, my mistake).

First Impressions :
It looks really nice, and I'm very excited. The only bad point seems to be the slowness of the interface : it takes ages to move big windows or drawers. But inside of them the text or anything else is really fast!

Oh, and I've been unable to set up my prism2 Wifi pccard, nor could I set up my 3Com e589 one. So no internet for my miggy up to now.

I hope this report will help some people who may have a few issues during the install process.

@TetiSoft
Quote:

Documentation/C/BootLoader doc explains which files are loaded etc. However, BootLoader will always load the OS4 kickstart files from disk, and they would probably not fit into the flash memory anyway.

I`ve read the docs, but found no specific instruction on which files are to be copied to flash rom...

Quote:

Kickflash reduces the boot time of classic Amigas dramatically, because it gets rid of all the reboots that today's Amigas have to do.

Has anybody managed to setup his flashrom? With Luciferin the files won`t be transfered to the flash rom because they don`t contain a valid RomTag or they`re not recognised as executables \

@Framiga
Quote:

IMHO (and re-reading your first post) the issue is related to your previous attempt to install BSD. What filesystem are you using? and have you used in the past HDInstalTools to prep that disk?

I`m using FFS (45.13 & 51.10), and the disk was set up as OS3.9 partition, WORK partition, and some free space (about 2,5 GB unformatted, reserved for future use : OS4/BSD)

Last edited by Cass on 04-Jan-2008 at 11:55 PM.

_________________
Ordell Robbie: Is she dead, yes or no?
Louis: Pretty much.

@stevieu

I got mine installed now.
I rebooted with the disk and cd, clicked on the harddisk icon, selected quick format, and then installed os4 skipping the part where it askes about formatting or partitioning the drive.
It then installed normally.
It wouldn't boot, saying it was a non DOS disk after that but as someone else wrote in this thread I had also forgotten to load the Fasfilesystem from disk and change the 3 to a 7.

@Anybody!



RE: Help!!



Trying to install on an A4000T/CyberPPC with HD on CyberPPC SCSI bus and CDROM on internal A4000T SCSI bus. Made copy of floppy and set echo on to see what was happening. Floppy can boot and does mount CD as I can see it make assigns to the CD. It then gets to the point where it loads the bootloader like this:

C:BootLoader COMMANDLINE "AllowBasepageAccess IgnoreCVPPC"



It seems to fail. The OS is still there. I can move the pointer, but nothing else happens.

IIRC, it reboots at one point and the whole process starts again.


Right now I am trying to copy the whole CD onto a HD volume to work around the problem. Then boot that! But, is is flaky as I get errors about files not there.



BTW, can OS4 be installed onto PFS3?




Edit: It freezes with black screen after trying to boot CD. Resetting gives me a Purple screen flash and then the system is stuck. I assume this is OS4 kernal as I have to turn off to get computer back.
Would any of these cards cause a problem?

DKB 128M Z3 memory expansion
GVP TBC
VLAB Motion
Toccata

Last edited by Hypex on 05-Jan-2008 at 11:51 AM.

Last edited by Hypex on 05-Jan-2008 at 10:07 AM.

@Hypex

dont use PFS as it is not supported, use SFS or FFS2

_________________

@Cass


Quote:

I`m using FFS (45.13 & 51.10), and the disk was set up as OS3.9 partition, WORK partition, and some free space (about 2,5 GB unformatted, reserved for future use : OS4/BSD)

i have no direct experience about FFS on latest AmigaOS variuos incarnations but (and here sorry if i'm stating some obvious things you already did)

Have you set FFS to accept long filenames? (DOS/7 IIRC)

Anyway i would try to install SFS (for the AOS4 partition at least)

_________________

@Derfs

Quote:

dont use PFS as it is not supported, use SFS or FFS2

The instructions say to use a filesystem with long filenames. which PFS supports. My friend just loves PFS, he says it is unbreakable! I have told him about SFS, but he isn't familar with it, so a bit hesitant to use it. I will pass that info on. Thanks.

Now just to get OS4 working on his machine, which it don't at all right now.