CompuServe Thread

Wshell2.0/conman

8 messages in this thread
#29214From: MICHAEL R. GROVEOct 14, 1992 9:57 AM
I have been using Wshell 2.0 for a while and decided to try some of the niceties. When I tried to use the Menu in DHopt, the error message came back that a version >37 was required. So, I checked out the libraries and found that my conman was 36 something. I like conman because of the F1/F2 keys for resizing. I checked with the latest version of conman in Compuserve and I have the latest version. Any suggestions?
#29221From: Michael SheaOct 14, 1992 12:31 PM
Michael, I am sure Bill will answer up here, but I think version 37 is referring to needing WB2.0. The manual says that some features of WShell 2.0 will not work with pre 2.0 ADOS. Also, looking at the beginning of section 4-5 on page 33 of the manual, is says "DisplayHandler allows user-configurable menus". Since you are using Conman vice DisplayHandler, this could also be your problem. You realize of course with WShell 2.0, Conman is no longer required. Also, I use Displayhandler and F1/F2 does resizing of my just like Conman did. Mike Shea……
#29236From: Bill HawesOct 15, 1992 7:18 AM
Michael, Console window menus are available only with AmigaDOS 2.0, as it provides the new system functions used for menu layout. If you request a 2.0-only option with the DHOpts command, it issues the warning message about the system library version. ConMan isn't needed with WShell 2.0 — the special features of WShell are designed to work with the DisplayHandler software. The WShell console menus will work once you've upgraded your OS software to AmgiaDOS 2.0. -Bill Hawes
#29243From: MICHAEL R. GROVEOct 15, 1992 12:36 PM
Ok, I'll reconfigure my startup-sequence without conman. I didn't see the resizing F1/F2 in the documents. Also, I am very used to the * wildcard ability. This isn't mentioned in the documents either.
#29290From: tom millerOct 17, 1992 9:10 AM
Michael, I don't think the * wildcard ever came from Wshell nor Conman. If I remember right, under WB1.3 the star was a feature of using ARP commands. Under WB2.0 it must be turned on by a utility in your startup. That program is in the libraries here. I use "starburst", but that is not the most popular and I dont think thats the name of the one here. -Tom
#29318From: Bill ThompsonOct 18, 1992 8:40 AM
Hi, Just picked up Wshell2.0 and I am really impressed!! I've gotten everything to work except the menus… no errors or anything, just no menus! BTW, I love the file name completion… almost worth the price of the package… and the path-handler really helps me keep the disk clean!! Thanx for a wonderful package! Bill… on Autopilot in Womelsdorf 😉
#29356From: Bill HawesOct 19, 1992 7:14 AM
Bill, The most common problems with WShell menus are (1) not having the AmigaDOS 2.04 software (required for WShell menus) and (2) referring to the menu pathname rather than the assigned menu name. When you load a menu description file, e.g. S:WShell/My_Menus, the DHOpts command strips away the path information and uses just the tail of the filename (My_Menus) as the menu name. This is the name you must use in your console definition in order to attach the menus, e.g. CON:0/0/600/100/My_Shell/MENU#My_Menus. Putting a full pathname in the console definition doesn't work. Glad to hear you're enjoying the filename completion and PathHandler! -Bill Hawes
#29771From: Bill ThompsonOct 31, 1992 10:34 AM
Thanx… I'll give it a try!! Bill… on Autopilot in Womelsdorf 😉