Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: rvo_nl on January 18, 2010, 06:43:21 PM
-
Im trying to get diropus 4.17 (pre 21) to work. It keeps messing up the menu, no matter what font I select in configopus. Here's what it looks like:
(http://www.vanooij.nl/FILES/diropus.jpg)
I know the picture is bad, but you can clearly see there is something missing in the menu. Program works fine otherwise.
I'ved tried moving all directories in PROGDIR: to some other place until only the executable remained, this still didnt help. There's nothing in my SYS:C/ S/ or whatever folders, as far as I can see. Snoopdos doesnt tell me anything either, all the libs that couldnt be found are now in PROGDIR:, to no avail.
This happens with the latest stable (4.16) aswell as the latest beta (4.17.21) although I'm pretty sure I had it working once with 4.16.
Any ideas?
-
I am sorry but 4.16 works fine here. No problems with menus whatsoever.
So it is something particular of your setup. Maybe you should try reinstalling Dopus, and by the way 4.17.21 is already out!
If it doesnt work then blame your AmigaOS setup as it probably has something hacky that is interfering with those Dopus menus.
-
hey gulliver, thanks for your reply. however, since I have just installed my machine I can guarantee you that I am not running any patches (yet)! Also, I am using .21, sorry for that. Corrected this in my post. Remember that a plain 4.16 install has the same problem. Ofcourse I did a manual and automatic install beforehand.
-
Hello,
I use DirectoryOpus 4.12CU addition, and it requires "DirectoryOpus.CFG" to reside in your S: directory. I'm guessing yours will too.
What happened to me was that I could configure DirOpus, but it never saved my settings, yet it said that it had (no error message upon save). Yet when I would quit the program and reload it....my settings would be gone (back to default).
Snoopdos was no help here, nothing ever showed up on snoopdos, infact when it reads the config file it doesn't show up on snoopdos....I just took a guess that the config file should belong in S: and I was right.
So I suggest moving the config file to your S: directory, and see if that fixes it. Good luck.
-
It is odd! Have you installed any BoingBags, or any software driver for any particular hardware? Have you installed AmigaOS 3.9 from the emergency floppy. Was it an upgrade from say 3.1 or 3.5?
-
well, the configfile is read from the progdir:s/ folder aswell, and thats where I keep it. I have done a clean install of OS3.9 (in fact I have done about 50 of 'em in the last months). Ofcourse I installed cybergraphx, warpup, warp3d, mui and ahi.
-
Hi,
Please see the attached grabs of my DOpus set up.
Check you have the correct files in the Directories as shown.
As you can see I'm running DOpus 4.17pre13.
Regards, Michael
aka rockape
-
Are you using the original DirOpus icon that came with the package?
If you updated the icon then the stack size would also need re-entering to whatever it was before.
-
if you have an old .catalog, delete it. Is not compatible with the latest versions
-
hmm some good advice there, thanks. Im using BB2, btw. I am using the icon from 4.16 since the 4.17 pre 21 archive didnt have one, iirc. but I will check again. thanks for the other tips and screenshots, really helpful! need to try some things tomorrow.
-
So, I uninstalled Diropus, removed everything diropus related, then reinstalled 4.16 using the installer. Copied some more stuff by hand to match rockape's screenshots. Looked for old catalogs and increased the stack. Rebooted, and started diropus..
This time only the first item of each menu appeared! Really strange. So then I copied my old 2002 .cfg file from diropus 4.13 (!) to s: and restarted. This time the menu's were correctly shown. I then removed everything diropus related, apart from the main program (still 4.16). Without my old .cfg file, the menu's appeared again. Although Snoopdos now reported a missing Topaz font, odd enough.
I then replaced 4.16 with the 4.17.21 beta and copied all files to progdir: again. without my old .cfg file, no menu's. With my old .cfg file, they now show up right.
a) looks like it is some setting in the config file then? No idea why its configged this way by default then. Any idea where I can find it? Ive tried fonts and colours. to no avail.
b) is it safe to use my old 4.13 config file with 4.17? it saves and loads okay..
-
a) looks like it is some setting in the config file then? No idea why its configged this way by default then.
Check if the file format of the config file was been changed [old <-> new].
x303 :D :D :D
-
sorry, dont know what you mean. you mean its extension?
-
sorry, dont know what you mean. you mean its extension?
Meant that the new config file might be corrupted.
If you can't get it working properly, why not try newfilemaster ? It's a little bit more up-to-date.
http://aminet.net/util/dir/NewFilemaster.lha
x303 :D :D :D
-
ha! no. I will stick with diropus. its a wonderful program. but thanks, I'll have a look.
-
ha! no. I will stick with diropus. its a wonderful program. but thanks, I'll have a look.
I think the answer to your problem is that the foreground & background colors are the same (grey). Just adjust one of them and the menus will be visible again.
x303 :D :D :D
-
I tried, but that didnt work. Anyway, I have done a clean install of 4.17.21 and then added some stuff (like the .HLP files) from the 4.16 archive. Still corrupt menu's. However I used my old config file and have started configuring the program. Looks like its working with the old config file!
-
I tried, but that didnt work. Anyway, I have done a clean install of 4.17.21 and then added some stuff (like the .HLP files) from the 4.16 archive. Still corrupt menu's. However I used my old config file and have started configuring the program. Looks like its working with the old config file!
Strange, I have 4.16 & 4.17 (hidden). 4.17 worked on my system, but 4.16 had those strange menuitems. Selecting a menuitem worked though. So it had to be the menu colors. Looks your problem still is a broken configfile.
Can you attach this file for testing purposes ?
x303 :D :D :D