Hyperion Entertainment Message Boards

I'll admit that booting into a driver with reduced features is not ideal. But it's WAY better than having to install a 4000 series RadeonHD card before a new install. Some of us are running the original 4000 series card that the X1000 came with, many have upgraded to a newer card since then. But perhaps the people in the worst shape would be those who bought their system with a newer card already installed.. They have no means of booting to the original radeon driver at all.

The choices that were made have nothing to do with me.. I do not speak for Hyperion nor AmigaKit.. I may occasionally speak _TO_ either of them, but at no time do I speak _FOR_ them. Neither of those companies is foolish enough to put me in that position.

I just offered a short explanation about some of the reasons why a limited driver was used. Once you consider the alternatives, it makes much better sense.


Have Fun!

@all

I i would like to complete my previous report
1. The preparation (adding a partition from spare space on the disk) was done from my boot partition using OS4.1 update 6
I used blocksize of 512 and SFS\02 and saved the partiotons configure as mountlist.
The result was a visible icon, which i formatted (quickformat) and the partition could be opened showing a trashbucket
I still wonder what made it work this time (for my other partitions there is no mountlist, and they sue blocksize 1024 lso with SFS\02

2. I then booted from the OS4.1FE CD and started install after chosing language & keyboard
i was rather surprised to have the opportunity again to use Media Toolbox here, and wondered if my previous not being able to follow the instructions was due to the fact that they werte intended for a new version if of MTB on the CD. Could not verify that
I did create an additional SWAP partition with this MTB. I guess that i could use the existing one instead, and maybe 2 SWAP partitions will confuse the system.
I did set boot check & chose a lower boot priority for the OS4.1FE partition as for the OS4.1 final partition
The install & copying process seemed to pregress & end normally
As a result of the boot priority choice, at the end of the install it was this OS4.1 Upd6 system that showed up.

Surprise: my FE partition showed up now as an icon dh3:uninitialised.
(Was very happy to not have chosen an other boot priority)

3. I still have tried to use UBoot to boot from the OS4.1 partition and at least see if the new partition is recognised as a boot partition
There seem to be 2 boot partitions indeed, they are not that simple to find, they are identified the same way , and i did not succeed to boot in OS4.1FE
This seems the thing to expect if the partition is uninitialised


Suggestion: Something as http://blog.hyperion-entertainment.biz/?p=210 (which i just found) adapted for the OS4.1FE


Questions:
- is MTB on the CD a new version? After using it, seems the same tom
- one or two SWAP partitions?

Continuing report.

1. did a new format of the dh23: OS4.1FE partition & an install with the OS4.1FE CD
2. Finally the icon is there (on my OS4.1 Updt 6 WB screen
clicking on it the system files ar there too.
3. using the early startup menu i choose to boot from dh3: OS4.1FE partition
the startup does not get past the AmigaOS4.1 svreen
4. using the early startup i chose dh3: again but with the CLI -only option
I get a shell saying its OS4.1FR
5. i type in loadwb
the WB appears, i was pleasantly surprised that it shows al/most? of my icons i had with OS4.1Upd system
6. tried to launch Amiupdate: no effect
retried 3. 4. 5.
This time when loadwb is doing its job i get a scaring mention of an error (location 440) on my (work) partition.
Rereading the partition does not help.

Restarting with OS4.1 Updt 6 gives me no such warning and i can use the dh1: partition.
Next step: i am going to buy an external HD before entering in Workbench mode again

Questions:
1 Why isn't the direct boot in workbench mode succesfull?