@MamePPCA1

OK thanks.

I will try it later when I get my copy of OS 4.0 Final downloaded and burned to a CD.

the phoenix project now has a home - but no content yet.

i remember that the pianeta hompage wrote that the phoenix project joins "dozens of Amiga OS4 programmers".
are they too shy to tell us who they are? and about their projects?
i mean "dozens" means at least two = 24 people. lets guess that 2 people work on one project - that would make 12 projects...

we know one of them - firefox. what are the others?

hey, guys. tell us more, please

byebye...

@MamePPCA1

Just install each version on seperate bootable partitions, and change the boot priority when you want to change versions, and re-boot.
Simple really.

@Swisso

Quote:

Sound Idea, I am not a developer but as an end user I would still wish for an auto-update feature in OS4.

It would be relativley easy for Simon to implement this as this is precisley what the program was designed and used for by the betatesters. AmiUpdate has to know where to find the updates, and if it is confined to one central repository such as the beta OS components the location can be hard coded in.

Quote:Again AmiUpdate has to know where to find the updates, and where the user has them installed. At the moment Simon keeps a database of the current versions and their locations on the AmiUpdate site, but he has to maintain that himself, it is not automatic.
Developers also ned to add code for AmiUpdate to their programs for AmiUpdate to check versions etc correctly.
If a program has an assign in user-startup, then AmiUpdate can use that to find it, if it is just installed in a progdir on the Amigas harddrive AmiUpdate has no way of finding it. Unless you scan the hard drive every time an update of a prorgam that may or maynot be installed on the users system has had an update. Not the Amiga way of doing things.

I am not a programmer, and I might not have explained everything correctly, but I think Simon has done a very good job on this, and eloquently solved several problems by hosting an update database himself.

@TMTisFree

So I have to make 4 dirs on DH0 and put each installation
on its corresponding dir?

I have to stay secure to make 2 or 4 systems running at the same time.

Once I install all does the computer responds to OS 4.0 Final or does it respond to all the versions installed?

In other words does the system use the more appropiate
version of OS 4.0 in order to get the best results?

When I know these things I can install both versions at once.

@Snuffy

Welcome back!

Bye,
TMTisFree

Hi @Snuffy

Yeh right, talking to myself or the A1200!

Anyway this spider just popped out of spout -- booga!

It hadn't any thing to do with batteries. The summer days caused stressing: the two year old LCD monitor failed, the keyboard failed, the battery holder failed. Jeans-Jaques at Amiga Center was very helpful. I didn't know what the extent of all summer overheating did ,so I wanted him to verify that the Uboot rom was was OK.

A1200 serial-in:
U-Boot 1.1.1 (Mar 3 2005 - 16:42:53), Build: 03/03/05

CPU: MPC7450 v2.1 @ 800 MHz
Board: AmigaOne
DRAM:
Information for SIMM bank 0:
Number of banks: 2
Number of row addresses: 12
Number of coumns addresses: 10
SIMM is registered
Supported burst lenghts: 8 4 2 1 PAGE
Supported CAS latencies: CAS 3
RAS to CAS latency: 3
Precharge latency: 3
SDRAM highest CAS latency: 750
SDRAM 2nd highest CAS latency: 0
SDRAM data width: 8
Auto Refresh supported
Refresh time: 2084 clocks
Bank 0 size: 128 MB
Bank 1 size: 128 MB

Slot 1: vacant
DIMM0_B0_SCR0 = 0x00e77f00
DIMM0_B1_SCR0 = 0x00e77f0FLASH: 0 kB
VGA: 0..
In: serial
Out: serial
Err: serial
SCSI: Error SCSI Controller (1000,000F) not found
Net: 3Com 3c920c#0
AT Keyboard initialized!
USB: scanning bus for devices... 3 USB Devices found

Bus 0: OK Bus 1: OK
Device 0: Model: WDC WD400BB-00JHC0 Firm: 05.01C05 Ser#: WD-WMAMA5497000
Type: Hard Disk
Capacity: 38166.6 MB = 37.2 GB (78165360 x 512)
Device 1: Model: WDC WD200BB-75D000 Firm: 05.03E05 Ser#: WD-WMAD1H139000
Type: Hard Disk
Capacity: 19073.4 MB = 18.6 GB (39062500 x 512)
Device 2: Vendor: AOPEN Prod.: DUW1616/ARR Rev: 1020
Type: Removable CD ROM
Capacity: not available
Device 3: Vendor: LITE-ON Prod.: CD-RW SOHR-1239 Rev: 2$0A
Type: Removable CD ROM
Capacity: not available
Press any key to interrupt autoboot: 0

First-level bootloader: entered main
First-level bootloader: got 3 valid boot sources
AmigaOS4 first-level bootloader.
Scanning HDD WDC WD400BB-00JHC0 WD-WMAMA5497000 05.01C05... Entered find_sec_
start
Reading sector 0
Reading sector 1
Found an HD
FLB: found something
FLB: SLB of length 27828; loading
found AmigaOS4 second level bootloader.
FLB: SLB loaded; now launching it
Loading .text @ 0x014000a0 (22464 bytes)
Loading .rodata @ 0x01405860 (2488 bytes)
Loading .eh_frame @ 0x01406218 (52 bytes)
Loading .got2 @ 0x0141624c (724 bytes)
Loading .data @ 0x01416520 (208 bytes)
Loading .sdata @ 0x014165f0 (16 bytes)
Clearing .sbss @ 0x01416600 (168 bytes)
Clearing .bss @ 0x014166a8 (3928 bytes)
A1 Second-level booter V2.
Idea, design and main co
Booting configuration AmigaOS4.0

Booga!

@MamePPCA1

I have an Update4, a Final, a Final+Update4 and a Final+July installations here.
What I have done is put each full installation in its dir. somewhere, backup (move) the current install and move the install you want to SYS: and then reboot. This is much simplier than tweaking the kickstart but takes some disk space.

Edit: forgot to say that it takes 3 clicks to change the installation (2 move and 1 reboot).

Bye,
TMTisFree

AmiUpdate should be expanded to an external Library so that 3th party program can check for updates.

For example if Yam chould call the lib then check for updates. That whould be better than it whould expire after a month, at the same time you whould be free from downloading and unpacking youre self.

RWO

@ikir

Completely second that, great proggy

@MamePPCA1

I have it installed, but due to the fact i can't use
3D hardware (Radeon9800 here) it will crash on GL.

But at least i got that far


You could try running Snoopy to see if it lacks a file
or chokes on some other thing

@ikir

I agree with you 100%

@daxb

Quote:
They can IMHO be used like a normal removable medium, e.g.
like a MO medium or a ZIP disk or a CD-RAM or a SmartMedia
card.
Quote:
I've already written that it makes a difference.
Try to create two partitions on an USB stick with Windows,
then you see that even other OSes believe that removable
media are something different than a harddrive.

Quote:
Of course its possible to create a RIGID disk block
on a REMOVABLE medium with those tools, even with Media
Toolbox. This doesnt change the fact that SFS will refuse
to handle such partitions. Use a MountList with LowCyl=0.

@nubechecorre
There is surely a difference between "very soon" and 4 weeks time, where we know that it is scheduled to materialize in 4 weeks

@nubechecorre

Quote:
The Mediator does not support DMA to main memory ergo you
cant use all PCI drivers which require DMA, e.g. eth3com.device,
uhci.usbhcd, lsi53c8xx.device and most soundcard drivers
wont work. Voodoo and Permedia2 PCI gfx boards should work,
the Radeon boards dont work ATM AFAIR.

@nubechecorre

I have pointrelease since last year and doesn't work.

does it work better under Amiga OS 4.0 Final?

@TetiSoft

Hmm... I thought CF-Cards can be used and will be detected as a normal harddrive. So removeable or not shouldn`t make a difference. As far as I know CF-Cards can also partitioning with HDToolBox or HDInstTools. So writing a RDB should be possible too.

Somebody else have such problems formating CF-Cards with SFS 1.267?

@Sir_Lucas

It has been confirmed at PianetaAmiga 2007 and it should be released very soon

@Raziel

On AmigaWorld.net someone describes me the Kickstart configuration file to run both on the same parttion.
Anyway I trust and I will trust on OS 4.0 and I will
try it to see how it works.

@gdg

Is it really confirmed or just a supposition ?? I cannnot seem to find any info about it on their official website.