|
Post by clay on Nov 21, 2019 3:32:38 GMT 1
I have just started using vDos and it is working excellent. I have got some old programs that I have coded years ago that I am still running and updating.
The only problem I have is that the programs must be coded in a propriety text editor as you also do the screen layouts and database table design in the same editor.
The problem I get is that the editor has CTRL shortcut keys which I use all the time. Here's the weird thing, some of them work and some of them don't.
ie. CTRL+X, Q, V, D, T, G, F & P all work fine.
CTRL+L, S, U, W, R & N do not work at all. CTRL+S is the main one I need as that is the save hotkey.
Has any body got any ideas why some of them work but others do not?
|
|
|
Post by Jos on Nov 21, 2019 9:11:16 GMT 1
Those Ctrl key combinations do work in other Windows programs? What if you test them with SCODE.COM? Jos Attachments:SCODE.COM (2.97 KB)
|
|
|
Post by clay on Nov 21, 2019 22:52:54 GMT 1
Those Ctrl key combinations do work in other Windows programs? What if you test them with SCODE.COM? Jos The CTRL key combinations work everywhere else, just not in the editor so it must be the editor program itself that is doing something funny. I don't know why other CTRL combinations work in the same editor though!?! I have been also using the editor for years in 32 bit Windows running NTDVM with no problem. I have attached the editor exe to this post just in case you have any other ideas. Just load it up and access all the menus by pressing F9.
|
|
|
Post by Jos on Nov 22, 2019 5:54:54 GMT 1
I ran BW, and the Ctrl key combinations worked just fine. What version of vDos do you use, is there perhaps any TSR program loaded before BW?
Jos
|
|
|
Post by emendelson on Nov 22, 2019 15:58:10 GMT 1
Just to confirm what Jos said: the Ctrl keys work perfectly in vDos in my system also.
|
|
|
Post by clay on Nov 22, 2019 23:54:46 GMT 1
I ran BW, and the Ctrl key combinations worked just fine. What version of vDos do you use, is there perhaps any TSR program loaded before BW? Jos Hi Jos, You are dead right, the are working correctly in vDos. I have Dos application which is strictly 8.3 filenames but I have found that using UNC paths I can get a total of 64 character for the combined path & filename which I really need. As I also have a deep directory structure a I have to put shares on the deeper levels of the directories so the whole path\filename fits in 64 chars. Unfortunately this doesn't work under vDos but it does work in vDosPlus. I could map all the shares/directory paths to a drive letter under vDos. I will try that soon, I just have to modify my code it do that where vDosPlus works off the bat. vDosPlus must be messing around with the keybaord a bit which I have read in the docs. The good thing is a can use vDos for my source code editing and VDosPlus to run the app. Problem solved. :-) Thanks for your help.
|
|
|
Post by emendelson on Nov 23, 2019 0:00:29 GMT 1
It would certainly have saved time and trouble if you had said at the start that you were not actually using vDos, but instead using vDosPlus. But it's good that you found the answer.
|
|