MyeditBR from Remote Desktop Connection
Moderators: Susan Smith, admin, Gabriel
i haven't been able to use MyEditBR on RDC for over a month. It simply won't launch. Luis tried reinstalling it - as his is the account that has the rights to do so and it works for him, but not for me.
It doesn't bother me too much because I use Notepad++. However MyEditBR does check for out of order line numbers, and that is convient sometimes. I rarely ever load it execpt for those situations - usually it's faster for me to renumber a range of lines than it is to load MyEditBR.
Sometimes I forget where all I've changed code in a huge program that I do not want to renumber.
Out of order line numbers cause a big hard to find problem when working in source.
And thus my wish:
I wish BR! would return an error when you try to merge source code that has out of order line numbers. (duplicate line numbers would be nice too)
-john
It doesn't bother me too much because I use Notepad++. However MyEditBR does check for out of order line numbers, and that is convient sometimes. I rarely ever load it execpt for those situations - usually it's faster for me to renumber a range of lines than it is to load MyEditBR.
Sometimes I forget where all I've changed code in a huge program that I do not want to renumber.
Out of order line numbers cause a big hard to find problem when working in source.
And thus my wish:
I wish BR! would return an error when you try to merge source code that has out of order line numbers. (duplicate line numbers would be nice too)
-john
John Bowman
MyEDIT BR - Automatic Updated.
It seems that the Update process does not work properly under RDP. We have 3.1.0.3166 installed on the Terminal Server.
When attempting to install I am notified there is a new version, but the update never installs.
I downloaded myeditbrv3setup.zip and extracted MyEditBRSetupV3.exe
Then I used the RDP "Add a Program' followed the wizard, and installed the program.
When prompted for the BR Support File locations I answered:
C:\Program Files\Mills Enterprise\MyEditBR\BRSupport.
This install routine worked properly. I received an error
Executable version 420 is greater than 413, ma allowed by license file.
Help and About in MyEDit BR showed version 3.1.0.3300
I noticed that I had an oder BRSERIAL.DAT, and replaced it with a new version.
Finally, I closed the MyEDIT application, an finished the Add Program Wizard.
After all of this, JB is now able to run MYEDITBR in RPD.
When attempting to install I am notified there is a new version, but the update never installs.
I downloaded myeditbrv3setup.zip and extracted MyEditBRSetupV3.exe
Then I used the RDP "Add a Program' followed the wizard, and installed the program.
When prompted for the BR Support File locations I answered:
C:\Program Files\Mills Enterprise\MyEditBR\BRSupport.
This install routine worked properly. I received an error
Executable version 420 is greater than 413, ma allowed by license file.
Help and About in MyEDit BR showed version 3.1.0.3300
I noticed that I had an oder BRSERIAL.DAT, and replaced it with a new version.
Finally, I closed the MyEDIT application, an finished the Add Program Wizard.
After all of this, JB is now able to run MYEDITBR in RPD.
-
- Posts: 291
- Joined: Fri Jun 19, 2009 9:01 am
- Location: Lawrence, Kansas
- Contact:
This conversation belongs on the MyEditBR support forum, not on the "Wish List" thread.
I *still* wish BR! could give an error when attempting to EDIT ~ a source code file with out of order line numbers.
Honestly, I'd rather not use MyEditBR at all, but it IS a convenient way to find line number problems.
I *still* wish BR! could give an error when attempting to EDIT ~ a source code file with out of order line numbers.
Honestly, I'd rather not use MyEditBR at all, but it IS a convenient way to find line number problems.
John Bowman
Both are good advice.
There is a nifty option for RDP:
%SystemRoot%\system32\mstsc.exe /console
Add the "/console" to the end of whatever the icon already points to, and it will invoke the "Console", this is essentially the same as logging directly into the console.
It also has the advantage of "Bypassing" the licensing, so if you run out of user licenses, you can still log into the server to maintain it. (You can only do this once, because the other 'Console' user gets kicked out. You actually take over wherever the user was.
There is a nifty option for RDP:
%SystemRoot%\system32\mstsc.exe /console
Add the "/console" to the end of whatever the icon already points to, and it will invoke the "Console", this is essentially the same as logging directly into the console.
It also has the advantage of "Bypassing" the licensing, so if you run out of user licenses, you can still log into the server to maintain it. (You can only do this once, because the other 'Console' user gets kicked out. You actually take over wherever the user was.
-
- Posts: 291
- Joined: Fri Jun 19, 2009 9:01 am
- Location: Lawrence, Kansas
- Contact:
-
- Posts: 717
- Joined: Sun Aug 10, 2008 4:24 am
- Location: Southern California
When I updated my MyEditBR recently, I also received the same licensing error that Luis mentioned (that was attributable to the wrong BRSERIAL.DAT file). Ryan explained it thusly:
Ryan Mills wrote:
"BRSupport.exe is a renamed copy of BRNative.exe When you installed MyEditBR you probably got presented with a question about your WBConfig.sys (or BRConfig.sys) file as well as your BRSerial.dat file.
Well I'm guessing that the installer found you already had a BRSerial.dat file in the MyEditBR\BRSupport folder. So it didn't replace it.
So the solution should be to copy your new v4.2 BRSerial.dat file into the MyEditBR\BRSupport folder, making sure to overwrite the existing file, and everything should start working again."
That did solve my problem. A remaining issue for me was that I have multiple BR folders (one for each client system). They have different versions of BR running and different BRCONFIG.SYS files - even with different file names. This has been a pain for MyEditBR when I go back and forth between clients. I have to remember to switch it in my MyEdit setup. But as I get phone calls from clients and have to quickly look up information, I can't take that time, and I find that I don't use MyEdit at those times, going back to the builtin BR editor instead.
I'm sure that my situation is different from others since I have no vertical application and each client system is widely different (and separate).
-- Susan
Ryan Mills wrote:
"BRSupport.exe is a renamed copy of BRNative.exe When you installed MyEditBR you probably got presented with a question about your WBConfig.sys (or BRConfig.sys) file as well as your BRSerial.dat file.
Well I'm guessing that the installer found you already had a BRSerial.dat file in the MyEditBR\BRSupport folder. So it didn't replace it.
So the solution should be to copy your new v4.2 BRSerial.dat file into the MyEditBR\BRSupport folder, making sure to overwrite the existing file, and everything should start working again."
That did solve my problem. A remaining issue for me was that I have multiple BR folders (one for each client system). They have different versions of BR running and different BRCONFIG.SYS files - even with different file names. This has been a pain for MyEditBR when I go back and forth between clients. I have to remember to switch it in my MyEdit setup. But as I get phone calls from clients and have to quickly look up information, I can't take that time, and I find that I don't use MyEdit at those times, going back to the builtin BR editor instead.
I'm sure that my situation is different from others since I have no vertical application and each client system is widely different (and separate).
-- Susan