Diskmaster2

AmigaDave · Post by **AmigaDave** » Thu Apr 12, 2012 6:57 am

Not sure if this is a problem with just the install of AmigaOS4.1.5 on my First Contact X1000 computer, or if Diskmaster2 comes pre-installed on all OS4.1.x systems. (I am new to OS4.x)

I tried to use the Archive menu item to unarchive to destination using Lha and nothing happens. When I closed Diskmaster2 I then saw a shell window open on the Workbench screen that had Diskmaster2 on the top edge and showed an error code 10 (IIRC).

Can someone tell me what I need to do to get the Lha functions built into Diskmaster2 to work on my new X1000. I would think that Diskmaster2 should be looking in the C drawer for the Lha command and if found there, it should work. Not sure if this is a Diskmaster2 fault, or an installation error, where maybe Diskmaster2 was not installed correctly on all of the First Contact X1000 computers?

Any ideas?

Post by **Slayer** » Thu Apr 12, 2012 9:31 am

Ok, I've just tested this and it works

I downloaded lha v2.15 which downloaded to DH1:DL/lhav2.15.lha

I extracted the lha executable to Sys:C

I opened DM2

In the left hand window I selected ram as the device and created a directory called test and clicked into it

Left window now displays RAM:Test

In the right hand window I clicked through to DH1:DL

I left click selected the lhav2.15.lha file

I then held down the right mouse button above the selected file and selected Archives then LHA X >dest

Instantaneously I got this listing in the left hand directory

lha
LhA.guide
lha_os4.readme

I also just tried it using the drop down menu, same result

Perhaps when you've been trying it you haven't had a valid destination directory in the "other" window?

I haven't looked too closely at it but I did notice that the command line could be updated to include -a3 look at the documentation to see what these options provide or just type lha in a shell for a quick listing

Hope this helps

and yes tested on X1000 AmigaOS 4.1.5

AmigaDave · Post by **AmigaDave** » Sat Apr 14, 2012 1:42 am

Thanks Slayer.

I will try to track down the problem with my system, or install of DM2. It was my file management tool of choice "back-in-the-day", as I found it simpler than D-Opus and easier to use.

I am sure it is something simple.

Also noticed something else that looks strange, and that is when I run SysConfig. I don't remember the exact output, but it is something like 6 lines of identical text that make no sense to me.

Post by **Slayer** » Sat Apr 14, 2012 7:59 am

They are simply just references to devices or expansions existing and/or installed and whether or not they are monitored as being working. Anyone in the know would be able to determine what is playing up by using these fields, or at least narrow the search, probably memory addresses and hex identifiers.

A hardware sniffer if you like?

That's my theory on the matter anyway

AmigaDave · Post by **AmigaDave** » Sun Apr 15, 2012 2:30 am

Slayer wrote:They are simply just references to devices or expansions existing and/or installed and whether or not they are monitored as being working. Anyone in the know would be able to determine what is playing up by using these fields, or at least narrow the search, probably memory addresses and hex identifiers.

A hardware sniffer if you like?

That's my theory on the matter anyway

Isn't it a little strange to include SysConfig in OS4.x when it does not work? If it works on other models of OS4.x hardware, I guess it does make sense to include it in any version of OS4.x, because there are not separate versions of OS4.x for each hardware type, like MacOS used to do with their separate versions which would not boot up on anything except the correct hardware that the certain MacOS version was designed for. Does SysConfig work properly on other OS4.x hardware, like the original AmigaOne systems, or perhaps the SAM systems? That is the only thing I can think of, that it works on those other OS4.x systems, but perhaps does not work on the X1000 yet because of some missing drivers and the different CPU, since it uses the PA6T and not a G3, or G4, but then the SAM does not have a G3, or G4 either.

I was just expecting SysConfig to show something that made sense, or to have it display an error message that it does not work YET on the X1000 hardware. Not a big deal, just something I noticed and wondered about. Back to the original question, I will check to see why Lha appears to work in other parts of OS4.x, but is not working properly from inside of DM2 when I try to use the drop down Archive menu. I'll report back what I find out.

Post by **Slayer** » Sun Apr 15, 2012 2:59 am

Amigadave I'm sorry but perhaps I should have said you need to expand the Amigashell window to see everything else that scrolled up prior to the last eight lines of digits and letters, I just didn't want to indirectly convey that you wouldn't have already known this. No harm done though; For example when I click on the middle box in the right hand corner I get this information in the now expanded Shell window:

Full Output from ShowConfig :

If you don't then there is something wrong and come back here and we'll look further into it

Hyperion Entertainment Message Boards

Diskmaster2

Diskmaster2

Re: Diskmaster2

Re: Diskmaster2

Re: Diskmaster2

Re: Diskmaster2

Re: Diskmaster2