Topic: Vista x64 SP1 Problems (1 of 29), Read 143 times
Conf: Installation, Configuration
From: Steven Borrok
Date: Tuesday, July 28, 2009 11:55 AM

I am currently running Vedit 6.15.3 under Vista x64 SP1 and have encountered the following problems:

1. If I click Help / VEDIT User's Manual, I get unsupported 16-bit application, followed by "CANNOT SHELL OUT. ERROR #88". I can bring the PDF manuals (user & macro) up no problem from Window Explorer.

2. Although I selected the "open with Vedit" context menu option on installation, it is not one of the choices on the context menu (right click in Windows Explorer).

Neither one of these problems are serious, just annoying. I have only been using Vista x64 for about 1 week. I haven't encountered any other problems at this time. I did try to go through the web board and could not find a solution to either of these problems. Any assistance that you can provide will be appreciated.

Note: I do not know how many VEDIT users are using Vista x64 but if you need a tester, let me know. I can do what I can to help.

 


Topic: Vista x64 SP1 Problems (2 of 29), Read 119 times
Conf: Installation, Configuration
From: Ian Binnie
Date: Tuesday, July 28, 2009 07:51 PM

On 7/28/2009 11:55:27 AM, Steven Borrok wrote:
>I am currently running Vedit
>6.15.3 under Vista x64 SP1 and
>have encountered the following
>problems:

1. If I click Help
>/ VEDIT User's Manual, I get
>unsupported 16-bit
>application, followed by
>"CANNOT SHELL OUT. ERROR #88".
>I can bring the PDF manuals
>(user & macro) up no problem
>from Window Explorer.

>I did try to go
>through the web board and
>could not find a solution to
>either of these problems. Any
>assistance that you can
>provide will be
>appreciated.

I believe this has been mentioned before.
This is because Vedit tries to open the pdf using a 16 bit API call. These are not supported by x64 (XP or Vista)

The following link discusses a related issue:-
http://webboard.vedit.com/read?49026,49

Maybe Ted could change this in the new Vedit.
There seems to be no reason the 32 bit Windows versions of Vedit is using 16 bit calls.

 


Topic: Re: Vista x64 SP1 Problems (3 of 29), Read 131 times
Conf: Installation, Configuration
From: Ted Green
Date: Wednesday, July 29, 2009 09:17 AM

At 07:52 PM 7/28/2009, you wrote:
>I believe this has been mentioned before.
>This is because Vedit tries to open the pdf using a 16 bit API call. These are not supported by x64 (XP or Vista)
>
>The following link discusses a related issue:-
>http://webboard.vedit.com/read?49026,49
>
>Maybe Ted could change this in the new Vedit.
>There seems to be no reason the 32 bit Windows versions of Vedit is using 16 bit calls.

I will look into that today.

Ted.

 


Topic: Re: Vista x64 SP1 Problems (4 of 29), Read 117 times
Conf: Installation, Configuration
From: Steven Borrok
Date: Thursday, February 25, 2010 01:16 AM

I was wondering if there was any progress on making Vedit more compatible with 64 bit Windows (Vista or 7)?

 


Topic: Vista x64 SP1 Problems (5 of 29), Read 109 times
Conf: Installation, Configuration
From: Peter Rejto
Date: Friday, March 19, 2010 12:38 PM

On 7/28/2009 11:55:27 AM, Steven Borrok wrote:
>I am currently running Vedit
>6.15.3 under Vista x64 SP1 and
>have encountered the following
>problems:

1. If I click Help
>/ VEDIT User's Manual, I get
>unsupported 16-bit
>application, followed by
>"CANNOT SHELL OUT. ERROR #88".
>I can bring the PDF manuals
>(user & macro) up no problem
>from Window Explorer.

2.
>Although I selected the "open
>with Vedit" context menu
>option on installation, it is
>not one of the choices on the
>context menu (right click in
>Windows Explorer).

Neither
>one of these problems are
>serious, just annoying. I
>have only been using Vista x64
>for about 1 week. I haven't
>encountered any other problems
>at this time. I did try to go
>through the web board and
>could not find a solution to
>either of these problems. Any
>assistance that you can
>provide will be
>appreciated.

Note: I do not
>know how many VEDIT users are
>using Vista x64 but if you
>need a tester, let me know. I
>can do what I can to help.


Hello Steven,

I am also an x64 Vedit user, although I use it on Win XP (x64).

I have adapted a the Vedit macro, VEDITPDF.VDM, to my Win XP (x64) operating system. Specifically, I have replaced the System(nnn,DOS) command by a short subroutine. This adaptation was not enough to run it from the Vedit {Help} menu. So, I added my initials to the adapted macro and run it from the {Misc, Load/exec user macro ..} menu. I shall upload, VEDITPDF_PAR.VDM and please let me know whether or not it does work for your system.

-peter

 


Topic: Vista x64 SP1 Problems (6 of 29), Read 113 times, 1 File Attachment
Conf: Installation, Configuration
From: Peter Rejto
Date: Friday, March 19, 2010 12:40 PM

Oops,
I forgot to check the "Attached file".
So, I try again,

 
Adaptation of VEDTPDF.VDM to (x84)

 


Topic: Vista x64 SP1 Problems (7 of 29), Read 109 times, 1 File Attachment
Conf: Installation, Configuration
From: Pauli Lindgren
Date: Thursday, March 25, 2010 11:48 AM

On 3/19/2010 12:38:42 PM, Peter Rejto wrote:
>On 7/28/2009 11:55:27 AM, Steven Borrok wrote:
>
>1. If I click Help
>>/ VEDIT User's Manual, I get
>>unsupported 16-bit
>>application, followed by
>>"CANNOT SHELL OUT. ERROR #88".
>>I can bring the PDF manuals
>>(user & macro) up no problem
>>from Window Explorer.
>
>
>Hello Steven,
>
>I am also an x64 Vedit user, although I
>use it on Win XP (x64).
>
>I have adapted a the Vedit macro,
>VEDITPDF.VDM, to my Win XP (x64)
>operating system. Specifically, I have
>replaced the System(nnn,DOS) command by
>a short subroutine. This adaptation was
>not enough to run it from the Vedit
>{Help} menu. So, I added my initials to
>the adapted macro and run it from the
>{Misc, Load/exec user macro ..} menu. I
>shall upload, VEDITPDF_PAR.VDM and
>please let me know whether or not it
>does work for your system.

Peter,

The problem with your version is that the user has to edit the macro depending on which version of Acrobat is installed. In addition, your macro expects Acrobat, while most people only have Adobe Reader.

I wonder why you have removed some of the code from the original macro? Is this the reason why it can not be run from Vedit Help menu?

Anyway, I now made a version that uses registry key
"HKEY_CLASSES_ROOT\Software\Adobe\Acrobat\Exe\(Default)"
This should work for most users, whether they have Acrobat or just the reader installed.

This version is based on the original veditpdf.vdm. Essentially, only the system call has been modified, so it should be compatible with the old version.
If the registry key is not found, the old method for calling associated app is used.

I added some Statline_Messages for debug. Maybe those should be removed from the final version.
In addition, I changed the text in the dialog box a bit, since
- Acrobat Reader is now called Adobe Reader
- You do not need to have .pdf files associated since the reader is called directly

This macro works fine on my computer, but I don't have 64-bit Windows.
So maybe Peter and Steven could test this?

--
Pauli

 
Test version for 64 bit Windows

 


Topic: Vista x64 SP1 Problems (8 of 29), Read 122 times
Conf: Installation, Configuration
From: Peter Rejto
Date: Thursday, March 25, 2010 02:20 PM

On 3/25/2010 11:48:00 AM, Pauli Lindgren wrote:
>On 3/19/2010 12:38:42 PM, Peter Rejto
>wrote:
>>On 7/28/2009 11:55:27 AM, Steven Borrok wrote:
>>
>>1. If I click Help
>>>/ VEDIT User's Manual, I get
>>>unsupported 16-bit
>>>application, followed by
>>>"CANNOT SHELL OUT. ERROR #88".
>>>I can bring the PDF manuals
>>>(user & macro) up no problem
>>>from Window Explorer.
>>
>>
>>Hello Steven,
>>
>>I am also an x64 Vedit user, although I
>>use it on Win XP (x64).
>>
>>I have adapted a the Vedit macro,
>>VEDITPDF.VDM, to my Win XP (x64)
>>operating system. Specifically, I have
>>replaced the System(nnn,DOS) command by
>>a short subroutine. This adaptation was
>>not enough to run it from the Vedit
>>{Help} menu. So, I added my initials to
>>the adapted macro and run it from the
>>{Misc, Load/exec user macro ..} menu. I
>>shall upload, VEDITPDF_PAR.VDM and
>>please let me know whether or not it
>>does work for your system.
>
>Peter,
>
>The problem with your version is that
>the user has to edit the macro depending
>on which version of Acrobat is
>installed. In addition, your macro
>expects Acrobat, while most people only
>have Adobe Reader.
>
>I wonder why you have removed some of
>the code from the original macro? Is
>this the reason why it can not be run
>from Vedit Help menu?
>
>Anyway, I now made a version that uses
>registry key
>"HKEY_CLASSES_ROOT\Software\Adobe\Acroba
>t\Exe\(Default)"
>This should work for most users, whether
>they have Acrobat or just the reader
>installed.
>
>This version is based on the original
>veditpdf.vdm. Essentially, only the
>system call has been modified, so it
>should be compatible with the old
>version.
>If the registry key is not found, the
>old method for calling associated app is
>used.
>
>I added some Statline_Messages for
>debug. Maybe those should be removed
>from the final version.
>In addition, I changed the text in the
>dialog box a bit, since
>- Acrobat Reader is now called Adobe
>Reader
>- You do not need to have .pdf files
>associated since the reader is called
>directly
>
>This macro works fine on my computer,
>but I don't have 64-bit Windows.
>So maybe Peter and Steven could test
>this?
>
>--
>Pauli
>
>


Pauli,


A big thank you !

I did not have time to study your macro.
So, here is my informal reaction.

This is exactly that I was after but could not get it. That is to say, I wanted an adaptation of VEDITPDF.VDM in the style of your aspell.vdm, but could not do it.

All that I tried to do, was to eliminate the DOS switch in the original version and keep as much of the rest as possible.


Once again, I have learned quit a lot from your aspell.vdm macro and thanks for both of your macros.

-peter

 


Topic: Vista x64 SP1 Problems (9 of 29), Read 129 times
Conf: Installation, Configuration
From: Steven Borrok
Date: Friday, March 26, 2010 01:21 AM

Sorry for the delay in my testing. I was stuck in another state for a few days.

I downloaded the new macro. I am currently running Windows 7 Home Premium x64. I have tested this several times, bouncing between user's manual and macro manual. Everything worked 100%. Using the same computer, I have tried this in a VM of Windows XP Home x32 and everything still worked 100%. Let me know if there is anything else I can do.

Thank you.

 


Topic: Vista x64 SP1 Problems (10 of 29), Read 127 times
Conf: Installation, Configuration
From: Peter Rejto
Date: Saturday, March 27, 2010 05:09 PM

On 3/26/2010 1:21:50 AM, Steven Borrok wrote:
>Sorry for the delay in my
>testing. I was stuck in
>another state for a few
>days.

I downloaded the new
>macro. I am currently running
>Windows 7 Home Premium x64. I
>have tested this several
>times, bouncing between user's
>manual and macro manual.
>Everything worked 100%. Using
>the same computer, I have
>tried this in a VM of Windows
>XP Home x32 and everything.
>still worked 100%. Let me
>know if there is anything else
>I can do.




Steven,

Thanks for sharing the good news with me.

Now, I would like to take you up on your offer of

>Let me know if there is anything else I can do.


I would appreciate your trying to run aspell.vdm. This Vedit Macro is Pauli's spell checker macro. That is to say the macro which launches the Atkinson spell checker, aspell.exe. Incidentally, do you have a spell checker and are you interested in one ?

Anyway, the reference to aspell.vdm on this Forum is
webboard.vedit.com\read?46343,84 and you can find the specifics there.


My reason for asking you to try this is that I have a hunch that basically, running aspell.exe and acrobat.exe from Vedit is the same problem. I also have a hunch that Pauli's VEDITPDF.VDM is written in the same style as his ASPELL.VDM.

Now let me remind you of my contribution again. I believe that the reason that you ended up with those error messages is that there was a DOS switch in the Sytem( ) command of the original VEDITPDF.VDM file. I also would like to mention
that I treated similar problems taking up Ian's suggestion.
So, if you are ready for the specifics then I would suggest to reread Ian's message in this thread, webboard.vedit.com/read?58880,31.

Looking forward to hearing your reactions,

-peter.

 


Topic: Vista x64 SP1 Problems (12 of 29), Read 122 times
Conf: Installation, Configuration
From: Steven Borrok
Date: Tuesday, March 30, 2010 03:08 AM

Peter,

I will gladly test the macro for you. I currently do not have aspell.exe. Is it possible to get a temporary copy for testing purposes?

Steve

 


Topic: Vista x64 SP1 Problems (13 of 29), Read 126 times
Conf: Installation, Configuration
From: Peter Rejto
Date: Tuesday, March 30, 2010 11:04 PM

On 3/30/2010 3:08:18 AM, Steven Borrok wrote:
>Peter,

I will gladly
>test the macro for you. I
>currently do not have
>aspell.exe. Is it possible to
>get a temporary copy for
>testing purposes?

Steve


Thanks Steve,

I would be glad to share my copy of aspell.exe version 6 with you. My problem is that I am not sure whether or not my copy is corrupted or not.

So, this is my suggestion. Download aspell.vdm either by googoling it or from this forum,

webboard.vedit.com/read?46343


There Pauli gives detailed instructions how to get, I believe, version 5. That is to say version 5 for windows.

In fact, I would like to learn about the error messages that you get by sending aspell.vdm on an impossible mission.
That is to say, on asking aspell.vdm to launch the aspell.exe program that is not installed. If all goes well,
then you should get a Statline Message saying that aspell.vdm could not find aspell.exe.


Thanks again,

-peter

 


Topic: Vista x64 SP1 Problems (14 of 29), Read 129 times
Conf: Installation, Configuration
From: Steven Borrok
Date: Wednesday, March 31, 2010 02:04 AM

Peter,

I installed aspell.vdm 1.4 on a fresh install of Vedit. I did NOT install ASPELL yet. I added the first 3 lines of spell.mnu to my user.mnu. I closed all Vedit sessions. I started Vedit with no file loaded. I choose "Check spelling" from my user menu. The "Spelling check" dialog box came up. When I choose [OK], Vedit returns a dialog box stating "DIRECTORY NOT FOUND: \dict". I will download apell from http://aspell.net next. I will install and let you know.

Steve

 


Topic: Vista x64 SP1 Problems (15 of 29), Read 137 times
Conf: Installation, Configuration
From: Steven Borrok
Date: Wednesday, March 31, 2010 02:56 AM

Peter,

I installed aspell. I am not sure if I installed the language file correctly. When I try to run aspell from User menu, I get dialog box. After I click [OK] on dialog box, I get the following error: "Unsupported 16-bit application...". Do you have your modified macro so that i may try it?

Steve

 


Topic: Vista x64 SP1 Problems (16 of 29), Read 136 times, 1 File Attachment
Conf: Installation, Configuration
From: Peter Rejto
Date: Wednesday, March 31, 2010 10:20 PM

On 3/31/2010 2:56:47 AM, Steven Borrok wrote:
>Peter,

I installed
>aspell. I am not sure if I
>installed the language file
>correctly. When I try to run
>aspell from User menu, I get
>dialog box. After I click
>[OK] on dialog box, I get the
>following error: "Unsupported
>16-bit application...". Do
>you have your modified macro
>so that i may try it?


Thanks Steve,

I am attaching my aspell.vdm.

I hope that it will solve your
"Unsupported 16-bit application...".
error message.

However, before you use it, please rename Pauli's to aspell_original.vdm. I have a hunch that my aspell.vdm is an edited version of the one of Pauli's. But I am no longer sure.

Now, I would like to give you a progress report on my end.
On my regular machine I am using Win XP, the 32 bit version,
that I shall call Win XP (32x).
I am using my other machine, that runs Win XP (64x) either as a backup machine or for diagnostic purposes.

My aspell.vdm runs on my Win XP (32x) machine like a charm.
However, on my Win XP (64x) machine I do get an error message about the dictionary. I believe that my error message is similar to yours. I shall try it again and report to you the exact message.


Thanks,

-peter.

 
Very slightly edited version of Pauli's

 


Topic: Vista x64 SP1 Problems (17 of 29), Read 144 times
Conf: Installation, Configuration
From: Ian Binnie
Date: Thursday, April 01, 2010 08:26 PM

On 3/31/2010 10:20:28 PM, peter rejto wrote:
>On 3/31/2010 2:56:47 AM, Steven Borrok
>wrote:
>My aspell.vdm runs on my Win XP (32x)
>machine like a charm.
>However, on my Win XP (64x) machine I do
>get an error message about the
>dictionary.

This is probably because aspell stores its dictionary in its program directory.

I may depend on which directory aspell is installed in.

 


Topic: Vista x64 SP1 Problems (18 of 29), Read 135 times
Conf: Installation, Configuration
From: Peter Rejto
Date: Friday, April 02, 2010 02:59 AM

On 4/1/2010 8:26:02 PM, Ian Binnie wrote:
>On 3/31/2010 10:20:28 PM, peter rejto
>wrote:
>>On 3/31/2010 2:56:47 AM, Steven Borrok
>>wrote:
>>My aspell.vdm runs on my Win XP (32x)
>>machine like a charm.
>>However, on my Win XP (64x) machine I do
>>get an error message about the
>>dictionary.
>
>This is probably because aspell stores
>its dictionary in its program directory.
>
>I may depend on which directory aspell
>is installed in.


Thanks Ian,

In other words, this is not a Vedit issue !

I shall do a little bit more thinking about this. Then I shall start a new thread in the, say, Other, General confernce.

-peter.

 


Topic: Vista x64 SP1 Problems (19 of 29), Read 123 times
Conf: Installation, Configuration
From: Pauli Lindgren
Date: Sunday, April 04, 2010 12:25 PM

On 3/31/2010 10:20:28 PM, peter rejto wrote:
>
>I am attaching my aspell.vdm.
>
>I hope that it will solve your
>"Unsupported 16-bit application...".
>error message.

Actually I made that change (removed the DOS option in sys() command) in January 2009. But it seems I did not post that version in VebBoard, only at my web page:
http://koti.mbnet.fi/pkl/vedit/aspell.htm

So, does it work with 64bit Windows?

>
>My aspell.vdm runs on my Win XP (32x)
>machine like a charm.
>However, on my Win XP (64x) machine I do
>get an error message about the
>dictionary. I believe that my error
>message is similar to yours. I shall try
>it again and report to you the exact
>message.

If you get an error message "Dictionary not found!", that is because you have not installed a dictionary for selected language.

The error message Steven got shows that the directory for Aspell was not found (an empty string). (/dict is a sub-directory in Aspell home directory). However, there should be an error message "Aspell.exe not found!" displayed on status line before that, with alert sound.

Have you installed Aspell and a dictionary in the 64 bit machine?
What happens if you enter the following as direct command:

Registry_Get_Item(1,"HKEY_LOCAL_MACHINE\SOFTWARE\Aspell\(Default)")

and then insert text register 1 somewhere to see the contents? It should be the Aspell home directory.

--
Pauli

 


Topic: Vista x64 SP1 Problems (22 of 29), Read 125 times
Conf: Installation, Configuration
From: Peter Rejto
Date: Sunday, April 04, 2010 08:34 PM

On 4/4/2010 12:25:48 PM,
>If you get an error message "Dictionary
>not found!", that is because you have
>not installed a dictionary for selected
>language.
>


1.:
>What happens if you enter the following
>as direct command:
>
>Registry_Get_Item(1,"HKEY_LOCAL_MACHINE\
>SOFTWARE\Aspell\(Default)")
>
>and then insert text register 1
>somewhere to see the contents? It should
>be the Aspell home directory.

Pauli, this works like a charm.

In fact, before getting your email, I have performed an experiment. I believe that my experiment is a refinement of yours. In any case, here it is:


//--------------------------------------------------
:ASPELL(dump dicts 2); list available dictionaries to andard out.:
Reg_Set(106, "cmd %comspec% /k ")
//Reg_Set(#51=Reg_Free," ") // #51 = Base directory of the ASPELL spelling checker program.
Registry_Get_Item(107,"HKEY_LOCAL_MACHINE\SOFTWARE\Aspell\(Default)")
// Reg_Set(107, "c:\program files (x86)\aspell\bin\aspell.exe")
// Reg_Set(107, "c:\program files\aspell\bin\aspell.exe")
Reg_Set(107,"\",APPEND)
Reg_Set(107,"bin\aspell.exe",APPEND)
//Reg_Set(#52=Reg_Free)
Reg_Set(105,`"`,INSERT)
Reg_Set(105,@(107),APPEND)
Reg_Set(105,`"`,APPEND)
Reg_Set(108," dump dicts ")
System(`|@(106) |@(105) |@(108)`)
Return
// This works like a charm in WinXP (32x). That is to say, it returns a set of dictionaries.
// However, it does not work in WinXP (64x). The Windows-NO Disk dialog box pops up, saying
// Exception Processing Message
c00000013 7c7ffffdddf5 etc etc.
// This seems to be in accordance with the aspell.vdm Statline Message saying: Dictionary not found.



2.:

>>Have you installed Aspell and a
>dictionary in the 64 bit machine?

Well I do not know !. In fact, this is the purpose of my experiments. Probably, I did not install the dictionaries properly. This is strange since the installation was untouched by human hands. (The next item would be to install them by hand.)

My next experiment would be to get the Version Number from aspell.exe. I have a hunch that this should be possible by adapting the content of T-Reg(108). But I am getting tired.

OOps. Now this is no longer a Vista x64 SP1 issue.
Could you start a new thread ?


Thanks for everything.

-peter.

 


Topic: Vista x64 SP1 Problems (23 of 29), Read 106 times, 1 File Attachment
Conf: Installation, Configuration
From: Peter Rejto
Date: Wednesday, April 07, 2010 09:51 AM

On 4/4/2010 12:25:48 PM, Pauli Lindgren wrote:

>Actually I made that change (removed the
>DOS option in sys() command) in January
>2009. But it seems I did not post that
>version in VebBoard, only at my web
>page:
>http://koti.mbnet.fi/pkl/vedit/aspell.ht
>m
>
>So, does it work with 64bit Windows?

Pauli,

GREAT ! NOW THE PIECES START TO FIT TOGETHER !

My short answer is that (I believe) that it does work.

My long answer is that at present I am in no position to give an experimental verification of my belief.
However I can give two pieces of independent supporting evidences.

Evidence 1.

I am taking the liberty of uploading my old VEDITPDF.VDM file. That is to say, my edited version of the original VEDITPDF.VDM macro that I used on my old Win XP (x64) machine that crashed about a year ago. There I made a similar change and it worked like a charm. More specifically, I made the change suggested by Ian.


Evidence 2.

I do not know the specifics of my previous crash. All that I know is that on one of the drives it was a software issue. So, I re installed Win XP (64x) on that hard drive.


Win XP (64x) assigned the letter h: to this hard drive and I decided not to change it.

Now the actual experiment.

System(`cmd %comspec% /c "h:\vedit\vedit60.pdf"`,SIMPLE+NOWAIT)

and I did get the manual.

In other words, after adjusting the drive letter from c: to h: it worked like a charm.


Finally, I would like to ask you to change the version number of your web page aspell.vdm.


Thanks for everything,

-peter

 
Old, edited VEDITPDF.VDM, diagnostics

 


Topic: Vista x64 SP1 Problems (24 of 29), Read 61 times, 1 File Attachment
Conf: Installation, Configuration
From: Peter Rejto
Date: Friday, May 28, 2010 01:57 PM

On 4/4/2010 12:25:48 PM, Pauli Lindgren wrote:

>Actually I made that change (removed the
>DOS option in sys() command) in January
>2009. But it seems I did not post that
>version in VebBoard, only at my web
>page:
>http://koti.mbnet.fi/pkl/vedit/aspell.htm
>--
>Pauli

Pauli,

I have just downloaded your aspell.vdm, January 2009, edition, from your website, above.

I took the liberty of changing V1.4 to V1.5 (and a possible other typo) and uploading it, presently as ASPELL_V1.5.VDM.

If you have already uploaded it to this forum, then my alpologies and of course I shall erase this message of mine.

Thanks as always.

-peter

 
Aspell.vdm from Pauli's website

 


Topic: Vista x64 SP1 Problems (11 of 29), Read 121 times, 1 File Attachment
Conf: Installation, Configuration
From: Peter Rejto
Date: Sunday, March 28, 2010 04:02 AM

On 3/25/2010 11:48:00 AM, Pauli Lindgren wrote:
>Peter,
>
>The problem with your version is that
>the user has to edit the macro depending
>on which version of Acrobat is
>installed. In addition, your macro
>expects Acrobat, while most people only
>have Adobe Reader.
>
>I wonder why you have removed some of
>the code from the original macro? Is
>this the reason why it can not be run
>from Vedit Help menu?
>
>Anyway, I now made a version that uses
>registry key
>"HKEY_CLASSES_ROOT\Software\Adobe\Acroba
>t\Exe\(Default)"
>This should work for most users, whether
>they have Acrobat or just the reader
>installed.
>
>This version is based on the original
>veditpdf.vdm. Essentially, only the
>system call has been modified, so it
>should be compatible with the old
>version.
>If the registry key is not found, the
>old method for calling associated app is
>used.
>
>I added some Statline_Messages for
>debug. Maybe those should be removed
>from the final version.
>In addition, I changed the text in the
>dialog box a bit, since
>- Acrobat Reader is now called Adobe
>Reader
>- You do not need to have .pdf files
>associated since the reader is called
>directly
>
>This macro works fine on my computer,
>but I don't have 64-bit Windows.
>So maybe Peter and Steven could test
>this?

Pauli,

I would like to give you progress report.

1.: In short your macro works like a charm.

Here are the details: I did put your macro into my USER_MACRO directory. Then I used the Vedit {Help} menu command to choose a Vedit Manual and pass it to the Acrobat Reader via your adaptation of VEDITPDF.VDM.


2.: I have also done some minor editing of your macro. So, I called your subroutine :LAUNCH ADOBE READER: and performed some minor editing on it. My aim was to emphasize the similarity between this macro and your ASPELL.VDM macro.

Specifically, I use T-Reg(#51) only for the Adobe Reader.
Then I use T-Reg(#52) for the "Project String". That is to say for the parameter that we wish to transmit to the Adobe Reader.

So my next project is to have a simplified model of your aspell.vdm and put it into such a scheme. Like just transmit the FILENAME predefined string to Aspell.exe.

3.: I am trying to upload my edited/commented version of
veditpdf.vdm.

-peter

 
slighly edited/commented vefrsion of PL.

 


Topic: Vista x64 SP1 Problems (20 of 29), Read 104 times
Conf: Installation, Configuration
From: Pauli Lindgren
Date: Sunday, April 04, 2010 12:39 PM

On 3/28/2010 4:02:05 AM, peter rejto wrote:
>
>
>2.: I have also done some minor editing
>of your macro. So, I called your
>subroutine :LAUNCH ADOBE READER: and
>performed some minor editing on it. My
>aim was to emphasize the similarity
>between this macro and your ASPELL.VDM
>macro.

It is not a subroutine, since it is not called.
It is just piece of code in the middle of the main program.
You do not use the label anywhere.

>
>Specifically, I use T-Reg(#51) only for
>the Adobe Reader.
>Then I use T-Reg(#52) for the "Project
>String". That is to say for the
>parameter that we wish to transmit to
>the Adobe Reader.

That only makes the code more complex without any benefit.
It is better to keep code as simple as possible, and to use only as many registers as needed.

You have also changed some comments and the text in the dialog box removing reference to Adobe Acrobat. However, the macro should work equally well both with Adobe Acrobat and with Adobe Reader. (Maybe someone could test the macro with Acrobat?)

>
>So my next project is to have a
>simplified model of your aspell.vdm and
>put it into such a scheme. Like just
>transmit the FILENAME predefined string
>to Aspell.exe.

You can not transmit the filename to Aspell.exe. Aspell does not use the filename.
Aspell works in pipe mode. That is, it reads the input from stdin and outputs the results to stdout.
In addition, several other parameters are needed in the command line. BAT file was originally used to overcome the limitation in command line length.

--
Pauli

 


Topic: Vista x64 SP1 Problems (21 of 29), Read 130 times
Conf: Installation, Configuration
From: Peter Rejto
Date: Sunday, April 04, 2010 02:06 PM

On 4/4/2010 12:39:56 PM, Pauli Lindgren wrote:
>On 3/28/2010 4:02:05 AM, peter rejto
>wrote:
>>
>>
>>2.: I have also done some minor editing
>>of your macro. So, I called your
>>subroutine :LAUNCH ADOBE READER: and
>>performed some minor editing on it. My
>>aim was to emphasize the similarity
>>between this macro and your ASPELL.VDM
>>macro.
>
>It is not a subroutine, since it is not
>called.
>
>You do not use the label anywhere.


Thanks Pauli, for fixing this up.

Now let me tell you in simple words what I was after.

I simply wanted to put a label on that part of your program that I did edit.

Incidentally, I also like you snippets.vdm very much and I have been wondering whether I should call it a snippet or a subroutine. So, subroutine is out, which does not mean that snippet is in.

Thanks again,

-peter

 


Topic: Vista x64 SP1 Problems (25 of 29), Read 39 times, 1 File Attachment
Conf: Installation, Configuration
From: Peter Rejto
Date: Wednesday, July 21, 2010 03:41 PM

On 3/25/2010 11:48:00 AM, Pauli Lindgren wrote:
>On 3/19/2010 12:38:42 PM, Peter Rejto
>wrote:
>>On 7/28/2009 11:55:27 AM, Steven Borrok wrote:
>>
>>1. If I click Help
>>>/ VEDIT User's Manual, I get
>>>unsupported 16-bit
>>>application, followed by
>>>"CANNOT SHELL OUT. ERROR #88".
>>>I can bring the PDF manuals
>>>(user & macro) up no problem
>>>from Window Explorer.
>>
>>
>>Hello Steven,
>>
>>I am also an x64 Vedit user, although I
>>use it on Win XP (x64).
>>
>>I have adapted a the Vedit macro,
>>VEDITPDF.VDM, to my Win XP (x64)
>>operating system. Specifically, I have
>>replaced the System(nnn,DOS) command by
>>a short subroutine. This adaptation was
>>not enough to run it from the Vedit
>>{Help} menu. So, I added my initials to
>>the adapted macro and run it from the
>>{Misc, Load/exec user macro ..} menu. I
>>shall upload, VEDITPDF_PAR.VDM and
>>please let me know whether or not it
>>does work for your system.
>
>Peter,
>
>The problem with your version is that
>the user has to edit the macro depending
>on which version of Acrobat is
>installed. In addition, your macro
>expects Acrobat, while most people only
>have Adobe Reader.
>
>I wonder why you have removed some of
>the code from the original macro? Is
>this the reason why it can not be run
>from Vedit Help menu?
>
>Anyway, I now made a version that uses
>registry key
>"HKEY_CLASSES_ROOT\Software\Adobe\Acroba
>t\Exe\(Default)"
>This should work for most users, whether
>they have Acrobat or just the reader
>installed.
>
>This version is based on the original
>veditpdf.vdm. Essentially, only the
>system call has been modified, so it
>should be compatible with the old
>version.
>If the registry key is not found, the
>old method for calling associated app is
>used.
>
>I added some Statline_Messages for
>debug. Maybe those should be removed
>from the final version.
>In addition, I changed the text in the
>dialog box a bit, since
>- Acrobat Reader is now called Adobe
>Reader
>- You do not need to have .pdf files
>associated since the reader is called
>directly
>
>This macro works fine on my computer,
>but I don't have 64-bit Windows.
>So maybe Peter and Steven could test
>this?
>
>--
>Pauli


Pauli,

I am back to your VEDITPDF.VDM file and my reason is that it did not work on my office computer.

It was easy to fix it. Essentially, I hard wired the path to my Acrobat programm.

Now I would like to give you a more detailed report. The source of my problem was that I do not have access to the Windows registry on my office computer. So,
I ended up with the CAN NOT SHELL OUT, ERROR NUMBER 65 message.



Therefore, I commented out your line 74, which says that

if (Registry_Get_Item(#51,"HKEY_CLASSES_ROOT\Software\Adobe\Acrobat\Exe\(Default)") > 0) {

.....


Then I looked up on my desktop how do I call my Acrobat program and pasted this path.



I am attaching the exact details. Here I used my previously edited version of your VEDITPDF.VDM file

My reason for editing your file was that I would like to use it as a template. So, I wanted to have additional references to the Vedit manual. I also wanted to incorporate a trick that I have learned from Christian'a OPENCURS.VDM file. (This trick says, essentially, that although Vedit does not allow the concatenation of strings in general, there is a special case when it does allow it.
The case of the arguments of the System( ) command.)


Anyway, previously I did cut up the usage of your Reg_Set(#51,...) into two pieces. Specifically, into Reg_Set(#51, ...) and Reg_Set(#52, ....). Now this turned out to be handy, inasmuch as it was only neccesary to change my Reg_Set(#51, ..) command only.


I am attaching my VEDITPDF.VDM. Incidentally, thank you for your pointing out that my previous editing introduced some new errors. I fixed up some of those, but of course, I do not know whether I did fix all of them.


-peter

 
Slightly edited Pauli Lindgren macro

 


Topic: Vista x64 SP1 Problems (26 of 29), Read 39 times, 1 File Attachment
Conf: Installation, Configuration
From: Pauli Lindgren
Date: Tuesday, August 10, 2010 01:41 PM

On 7/21/2010 3:41:43 PM, peter rejto wrote:
>
>
>Now I would like to give you a more
>detailed report. The source of my
>problem was that I do not have access to
>the Windows registry on my office
>computer. So,
>I ended up with the CAN NOT SHELL OUT,
>ERROR NUMBER 65 message.

Yes, it seems that if you do not have administration rights for your computer, you can not access (even read) the branch "HKEY_CLASSES_ROOT" in the registry.

In fact, you can not even associate file types to Vedit, and Vedit can not be added in the registry so that it would show in "Add/remove programs" in Control Panel.

I now made a version that calls cmd.exe to use associated application in case the registry key is not found. This should fix the problem. The new version is attached.


>
>Therefore, I commented out your line 74,
>which says that
>
>if
>(Registry_Get_Item(#51,"HKEY_CLASSES_ROO
>T\Software\Adobe\Acrobat\Exe\(Default)")
>>> 0) {

You can not just comment out an "if" line.
That causes a program flow control error.
Instead, you should replace it for example with "if (1) {...".

--
Pauli

 
VEDITPDF(3).VDM (4KB)

 


Topic: Vista x64 SP1 Problems (27 of 29), Read 20 times
Conf: Installation, Configuration
From: Peter Rejto
Date: Wednesday, January 12, 2011 11:14 PM

Pauli,

I am studying your VEDITPDF(3).VDM macro again.

Suppose I set T-reg 103 by running {Help, Macro Language manual}.

Then I would like to run your comand on your line, I believe, 83. In other words, I wouuld like to run the command:


System(`start "|(HOME)\|@(103)"`,DOS+SIMPLE+NOWAIT)



Nothing happens. My problem is the start string in the argument of the System( ) command. If I omit this start string, it works like a charm.

Am I missing something ?


Thanks as always.


-peter

 


Topic: Vista x64 SP1 Problems (28 of 29), Read 23 times
Conf: Installation, Configuration
From: Peter Rejto
Date: Thursday, January 13, 2011 03:04 PM

On 1/12/2011 11:14:28 PM, peter rejto wrote:
>Pauli,
>
>
>
>System(`start
>"|(HOME)\|@(103)"`,DOS+SIMPLE+
>NOWAIT)
>
>
>
>Nothing happens. My problem is
>the start string in the
>argument of the System( )
>command. If I omit this start
>string, it works like a charm.
>
>Am I missing something ?
>
>
>Thanks as always.
>
>
>-peter

Pauli,

After correcting an error in my USTARTUP.VDM file, I do get a response to your command. Specifically, after entering

System(`start "|(HOME)\|@(103)"`,DOS+SIMPLE+NOWAIT)


in Command Mode, Windows opens up a cmd box. However, nothing happens In other words, the above command has the same effect as

System(`start "|(HOME)`,DOS+SIMPLE+NOWAIT).



Incidentally, I noticed that this command still has the DOS option, unlike your previous command. Is this on purpose.


Thanks as always.

-peter

 


Topic: Vista x64 SP1 Problems (29 of 29), Read 26 times
Conf: Installation, Configuration
From: Pauli Lindgren
Date: Saturday, January 15, 2011 06:39 AM

On 1/12/2011 11:14:28 PM, peter rejto wrote:
> Pauli,
>
> I am studying your VEDITPDF(3).VDM macro again.
>
> Suppose I set T-reg 103 by running
> {Help, Macro Language manual}.
>
> Then I would like to run your comand on your line,
> I believe, 83. In other words, I
> wouuld like to run the command:
>
> System(`start "|(HOME)\|@(103)"`,DOS+SIMPLE+NOWAIT)
>
> Nothing happens. My problem is the start string in the
> argument of the System( ) command. If I omit this start
> string, it works like a charm.
>
> Am I missing something ?

Are you using Windows 95, 98 or ME?
The "start..." command is only used with those (or older) versions of Windows.

If you are using NT, XP, Vista or Win-7, you should use one of the other two commands above that line in veditpdf.vdm.
That is why the macro checks the OS with "if (Is_WinNT)...".

--
Pauli