AmigaOS 4.1 FE update 2

[Saghalie]

Originally Posted by Yoji

I did use a "Create copy" of the preconfigured "Amiga 4000 PPC"... and used the copy to install my OS 4.1 FE... I assume that creates a copy of the 750MB hdf.... but have not double checked.
Cheers

Yes this does create a copy; but the 750mb hdf I have found is too small. I
usually create a new HDF which is about 900mb and after that have no
issues with install.

A little off topic but maybe could help?

[Yoji]

Originally Posted by Saghalie

No problems here. The only difference for me was that instead of using the
"LHA x update.lha" method, I just double clicked the icon for the download
and extracted/installed that way.

Interesting to note though is that I kept getting a guru for the file selector
but I would kill the process restart it and it ran without problems
afterwards.

Interesting.. so I guess by double clicking.. you didnt use LHA... and would have used the UnArc app..
Where did you UnArc it to?
As I said right at top of this thread.. I did try and use UnArc but it failed with the hang
But I just retired it.. using your method of just double clicking.. and again - I changed the destination (seemed to default to "system:") to Shared: and again, it progressed to about half way - and then just stopped and hung (I could not close the window/stop etc)..
P.S. I got no Guru/errors from the file selector.

And just to confirm.. after killing process in windows task manager and restarting system... I tried to delete the folder with the partial extract and that got to 28% complete.. and hung as well
So will delete the partial extract from within windows.. and do some retests.. but it looks like something is FUBAR.

Cheers

[Saghalie]

I UnARc'd to the RAM DISK:

I think the Shared drive is what is causing your issue. I'll see what happens if I use a shared drive (directory).

EDIT:
Yeah, it locked up on me and froze about half way through.

EDIT 2:
OK
==
I figured that since OS4.1FE is not really optimized for emulated systems we
would have issues with the Shared drive and never tried it until now.
What I have found (I'm usually wrong about these things so take it with agrain of salt) is that with AF the shared drive is not optimized for
long filenames. I tested it out and I found that:
1. If I change nothing the program halts about half way through and the
emulation freezes.
==
2. If I change the name of the archive file to Update2.lha (as you did) it un-
arc's to wherever you want it to with the long filename directory and if
I run the program I get GURU's on the filerequester and the setrx commands
as well as the emulation freezing - if I try and run it multiple times I usually
succeed - but that just sucks.
==
3. If I change the name of the archive to Update2.lha and UnArc it to the
Shared: drive (using the UnArc'iver) and then rename it to Update2 (or some
other shorter name) then the program runs just fine and the update occurs
like it should.
****
See if this works for you!

[Daedalus]

While shared drive behaviour is close to native behaviour, even under OS 3 emulation it occasionally does strange things so I tend to use virtual hard drives for System and Work partitions, and shared drives for data. It might be worth taking that approach for OS4 too...

[Yoji]

Originally Posted by Saghalie

I UnARc'd to the RAM DISK:

I think the Shared drive is what is causing your issue. I'll see what happens if I use a shared drive (directory).

Originally Posted by Daedalus

While shared drive behaviour is close to native behaviour, even under OS 3 emulation it occasionally does strange things so I tend to use virtual hard drives for System and Work partitions, and shared drives for data. It might be worth taking that approach for OS4 too...

Thanks to you both... I agree, I think the shared drive is suspect (although the RAM disk filling up in the way it did was also a bit weird).
I have emailed AmigaForever support to ask them... as they do set this drive up as part of their image for the OS4.1 system.. so should be interested and can perhaps fix in future (or use virtual hard drives and find a better way to share data with host system).
My experience still slightly different to yours Saghalie on your test 2.. where I was not able extract (it hung part way through extracting to shared.. but I have not seen any guru's on any file requestors. but may be our scenarios are not quite the same (I am not trying actually run the install prog.. I am just limiting my tests to extracting)

Thanks again for your help and input.
Cheers