Topic: "Waiting for Disk" and :CLEANUP: issue (1 of 10), Read 22 times
Conf: Startup, File Open, Exit
From: John H
Date: Monday, May 21, 2007 04:26 PM

Hi,
These don't seem to be related..

I decided to try 6.15.1 (3/30/06) on a new WXP based notebook and
got a tasted of some of the new things -- err actually I have not
looked over anything new that I want to yet since I have this
nagging problem.

I run windows defender (a MS malware detector) on the notebook and
it repeatedly warns me about the cleanup RUNONCE HKEY being set. I
permit it naturally, but the 'location' of the key is always unique
so I have to accept it each time. I don't know how to deal with that
specifically (unique key name each time) so I just commented the
:CLEANUP: lines in startup.vdm. There -might- be a way to make the
MS windows defender allow anything buy VPW.EXE but I've only breifly
looked for this sort of option.

My second and biggest issue is that when opening a file to edit via
VPW.EXE command line or with the registry 'open with vedit' shortcut
option of vedit, I get "Waiting for Disk.." for a couple/few
seconds -- even if the edit file is a 1K .txt file.

This does not happen with the version listed in the sig below. Nor
does it happen if I open the file from within an already running
instance of VPW.EXE.

This is the only installation of VPW (32-bit) 6.15.1 (3/30/06) so I
don't have any comparison with another version of Windows, etc.

--
John
VEDIT SN: 95651
VEDIT (DOS) Ver. 6.13.1 01/25/05
VEDIT (32-Bit) Beta Test Ver. 6.15.1 11/14/05
VEDIT Pro (64-Bit) Ver. 6.13.1 01/25/05
Windows 2000 (5.0.2195 Service Pack 4)

 


Topic: RE: 'Waiting for Disk' and :CLEANUP: issue (2 of 10), Read 28 times
Conf: Startup, File Open, Exit
From: John H
Date: Monday, May 21, 2007 05:42 PM

Okay, a little more info.. As you all probably already know, this seems to have something to do with the instance control, DDE, or whatever.

In the previous message I had instance set to "1" -- setting this to "0" removed the delay from the registry/shell feature "Open with Vedit".

Regarding 'temp' files.. don't the {filename.ext}.nnnn.#nn files constitute temp files?

These remain in the opened file directory, kind of figured that they would be in my choosen %TEMP% as per the default VEDIT install.

John


NOTE TO SELF: ALWAYS use e-mail to post/reply -- this webboard is a PITA. ;)

 


Topic: Re: "Waiting for Disk" and :CLEANUP: issue (3 of 10), Read 15 times
Conf: Startup, File Open, Exit
From: Christian Ziemski
Date: Monday, May 21, 2007 06:01 PM

On Mon, 21 May 2007 16:26:00 -0400, John H wrote:

>I decided to try 6.15.1 (3/30/06)
>
>I run windows defender (a MS malware detector) on the notebook and
>it repeatedly warns me about the cleanup RUNONCE HKEY being set. I
>permit it naturally, but the 'location' of the key is always unique
>so I have to accept it each time. I don't know how to deal with that
>specifically (unique key name each time) so I just commented the
>:CLEANUP: lines in startup.vdm.

John:

What do you mean with 'location'? Can you give examples?

On my Win2000 box the RUNONCE key is always created in the same place,
with the same name. (Tomorrow I'll check that on XP.)


And on Mon, 21 May 2007 17:34:00 -0400, you wrote:

>Regarding 'temp' files.. don't the .nnnn.#nn files constitute temp files?
>
>These remain in the opened file directory, kind of figured that
>they would be in my choosen %TEMP% as per the default VEDIT install.

They shouldn't remain after VEDIT quits.

What is your setting in VEDIT's menu
{Config, File handling, Use temp file directory}?

The online help of the above config entry describes the behaviour in
detail.


What is your environment variable TEMP set to?


Christian

 


Topic: "Waiting for Disk" and :CLEANUP: issue (5 of 10), Read 18 times
Conf: Startup, File Open, Exit
From: John H
Date: Tuesday, May 22, 2007 05:36 PM

On Mon, 21 May 2007 18:03:22 -0400 GMT, Christian Ziemski wrote:

> On Mon, 21 May 2007 16:26:00 -0400, John H wrote:

>>I decided to try 6.15.1 (3/30/06)
>>
>>I run windows defender (a MS malware detector) on the notebook and
>>it repeatedly warns me about the cleanup RUNONCE HKEY being set. I
>>permit it naturally, but the 'location' of the key is always unique
>>so I have to accept it each time. I don't know how to deal with that
>>specifically (unique key name each time) so I just commented the
>>:CLEANUP: lines in startup.vdm.

> John:

> What do you mean with 'location'? Can you give examples?

> On my Win2000 box the RUNONCE key is always created in the same place,
> with the same name. (Tomorrow I'll check that on XP.)

Sorry my mistake here. I kept having to 'permit' the runonce key to
be set when starting vpw.exe, I thought the HKCU@x-x-x-xx-xxx-etc
part had changed but looking over the recent history of windows
defender I can't see/find the key that made me believe that the
location was changing. Perhaps my brain concluded that it was
different since I am required to 'permit' the key to be set each
time, despite having allowed it previously.

Some tweak in WD perhaps I can find to avoid the need to confirm
after a reboot..

> And on Mon, 21 May 2007 17:34:00 -0400, you wrote:

>>Regarding 'temp' files.. don't the .nnnn.#nn files constitute temp files?
>>
>>These remain in the opened file directory, kind of figured that
>>they would be in my choosen %TEMP% as per the default VEDIT install.

> They shouldn't remain after VEDIT quits.

> What is your setting in VEDIT's menu
> {Config, File handling, Use temp file directory}?

> The online help of the above config entry describes the behaviour in
> detail.

> What is your environment variable TEMP set to?

Sorry I wasn't really clear here, I don't mean they remain after
closing vedit. I meant that the creation of these files is in the
same location as the file being edited. They are being removed once
closing the file or vedit. Just wondering if they should be created
in the %TEMP% area?

My TEMP:

USER = %USERPROFILE%\Local Settings\Temp
SYSTEM = %SystemRoot%\TEMP

--
John

 


Topic: Re: "Waiting for Disk" and :CLEANUP: issue (4 of 10), Read 15 times
Conf: Startup, File Open, Exit
From: Ted Green
Date: Tuesday, May 22, 2007 02:22 PM

At 04:31 PM 5/21/2007, you wrote:
>I run windows defender (a MS malware detector) on the notebook and
>it repeatedly warns me about the cleanup RUNONCE HKEY being set. I
>permit it naturally, but the 'location' of the key is always unique
>so I have to accept it each time. I don't know how to deal with that
>specifically (unique key name each time) so I just commented the
>:CLEANUP: lines in startup.vdm. There -might- be a way to make the
>MS windows defender allow anything buy VPW.EXE but I've only breifly
>looked for this sort of option.

I have Windows Defender installed on some computers, and have never seen this warning. Also the "location" should always be the same.
Removing the code from startup.vdm is certainly a solution.

>My second and biggest issue is that when opening a file to edit via
>VPW.EXE command line or with the registry 'open with vedit' shortcut
>option of vedit, I get "Waiting for Disk.." for a couple/few
>seconds -- even if the edit file is a 1K .txt file.

This has been reported before, about 4 years ago, and I don't remember the solution. VEDIT 6.15 under WinXP is the most common configuration with virtually no known problems.

Ted.

 


Topic: "Waiting for Disk" and :CLEANUP: issue (6 of 10), Read 17 times
Conf: Startup, File Open, Exit
From: John H
Date: Tuesday, May 22, 2007 05:55 PM

On Tue, 22 May 2007 14:24:48 -0400 GMT, Ted Green wrote:

> At 04:31 PM 5/21/2007, you wrote:
>>I run windows defender (a MS malware detector) on the notebook and
>>it repeatedly warns me about the cleanup RUNONCE HKEY being set. I
>>permit it naturally, but the 'location' of the key is always unique
>>so I have to accept it each time. I don't know how to deal with that
>>specifically (unique key name each time) so I just commented the
>>:CLEANUP: lines in startup.vdm. There -might- be a way to make the
>>MS windows defender allow anything buy VPW.EXE but I've only breifly
>>looked for this sort of option.

> I have Windows Defender installed on some computers, and have
> never seen this warning. Also the "location" should always be the
> same. Removing the code from startup.vdm is certainly a solution.

Hmm. With :CLEANUP: uncommented I must confirm/permit the RUNONCE
key to be set upon first run of vedit after a reboot. Do you recall
having to set something elsewhere to keep from having to confirm as
I am?

I don't run anything else on the machine in the form of idiot
proofing the system, aside from the fact that I have not turned off
the built in WXP system recover junk. NO major deal but it would be
just as well to allow the cleanup.bat to do it's job if the need
arises. I just don't feel like permitting it to set the key each
time I first run vedit after a boot.

>>My second and biggest issue is that when opening a file to edit via
>>VPW.EXE command line or with the registry 'open with vedit' shortcut
>>option of vedit, I get "Waiting for Disk.." for a couple/few
>>seconds -- even if the edit file is a 1K .txt file.

> This has been reported before, about 4 years ago, and I don't
> remember the solution. VEDIT 6.15 under WinXP is the most common
> configuration with virtually no known problems.

I've only the default installation, nothing in the way of my custom
version of another computer. It's entirely predictable though.

If instances is 0 (set via config menu) there is no delay whatsoever
but to open multiple files in one instance I must apparently use the
'Open with Vedit' right click option that is optionally added. While
workable it's a chore compared to my normal approach which is to
simply launch an edit session via my file manager using the
keyboard or though command line.

Setting the instances to 1 introduces the few second "Waiting for
Disk" delay if opening a file to edit and running vedit at the same
time. ie: vpe.exe something.txt

FWIW, the notebook uses Windows XP Media Center Edition 2002 - SP2

--
John

 


Topic: "Waiting for Disk" and :CLEANUP: issue (7 of 10), Read 21 times
Conf: Startup, File Open, Exit
From: John H
Date: Tuesday, May 22, 2007 09:04 PM


> I've only the default installation, nothing in the way of my custom
> version of another computer. It's entirely predictable though.

> If instances is 0 (set via config menu) there is no delay whatsoever
> but to open multiple files in one instance I must apparently use the
> 'Open with Vedit' right click option that is optionally added. While
> workable it's a chore compared to my normal approach which is to
> simply launch an edit session via my file manager using the
> keyboard or though command line.

> Setting the instances to 1 introduces the few second "Waiting for
> Disk" delay if opening a file to edit and running vedit at the same
> time. ie: vpe.exe something.txt

> FWIW, the notebook uses Windows XP Media Center Edition 2002 - SP2

Just wanted to add that the delay is also present with the:

VEDIT (32-Bit) Beta Test Ver. 6.15.1 11/14/05

..on the XP MCE SP2 machine so it seems that there is apparently
something different between the OS DDE or whatever. No delays
whatsoever on the W2K machine.

rant
I'd glady replace the XP with W2K if possible but I don't think that
machine would even work properly without WXP.. I've only began using
XP with this new notebook (bought 6-8 months ago) and now MS want's
to ram vista down my throat. What they don't seem to realize is that
I'd rather run 95SR2/98SE/2000 than any flavor of XP and I have zero
interest in vista.
/rant

--
John

 


Topic: No Topic (8 of 10), Read 21 times
Conf: Startup, File Open, Exit
From: Pauli Lindgren
Date: Thursday, May 24, 2007 09:45 AM

On 5/22/2007 5:55:52 PM, John H wrote:
>
>If instances is 0 (set via config menu)
>there is no delay whatsoever
>but to open multiple files in one
>instance I must apparently use the
>'Open with Vedit' right click option
>that is optionally added. While
>workable it's a chore compared to my
>normal approach which is to
>simply launch an edit session via my
>file manager using the
>keyboard or though command line.
>
>Setting the instances to 1 introduces
>the few second "Waiting for
>Disk" delay if opening a file to edit
>and running vedit at the same
>time. ie: vpe.exe something.txt

I can confirm that. I am using Windows XP Pro SP2. If Instance Control is set to 1, there is about 4 seconds delay whenever I open a file from Windows Explorer or from DOS prompt. If Instance Control is set to 0 or 2, there is no delay.

However, I can see very little reason to use instance control 1. In fact, 0 is more flexible. With setting 0, you can choose if you want to open the file in the same or different instance, e.g. by using drag and drop. In addition, drag and drop works with all files, not just with those that have been associated to Vedit.

If you drag a file into existing Vedit instance, the file is opened in that instance. If you drag the file into Vedit's desktop icon, a new instance is opened.

When using command line, you can control the instances with -s option.

The following test may reveal something about what is happening:
Set the instance control to 1.
While an instance of Vedit is open, drag a file onto Vedit desktop icon.
What happens?
First, a new instance of Vedit is opened. Then there is few seconds delay with "Waiting for disk" message. Then the new instance is closed and the file is opened in the old instance.

--
Pauli

 


Topic: No Topic (9 of 10), Read 24 times
Conf: Startup, File Open, Exit
From: John H
Date: Thursday, May 24, 2007 07:14 PM

On Thu, 24 May 2007 09:46:35 -0400 GMT, Pauli Lindgren wrote:

Hi Pauli,

> If you drag a file into existing Vedit instance, the file is
> opened in that instance. If you drag the file into Vedit's desktop
> icon, a new instance is opened.

Hmm. Aside from drag/drop not being well suited for keyboard control
of windows, I have never really used drag/drop much since I am so
accustomed to using my file manager application -- which is well
suited for keyboard (and mouse..) control. Not much chance I'm going
to adopt d/d just to work around this one quirk. :)

> When using command line, you can control the instances with -s option.

The delay is introduced when using the -s option.

--
John

 


Topic: No Topic (10 of 10), Read 26 times
Conf: Startup, File Open, Exit
From: Ian Binnie
Date: Thursday, May 24, 2007 08:44 PM

On 5/24/2007 9:45:37 AM, Pauli Lindgren wrote:

>I can confirm that. I am using Windows
>XP Pro SP2. If Instance Control is set
>to 1, there is about 4 seconds delay
>whenever I open a file from Windows
>Explorer or from DOS prompt. If Instance
>Control is set to 0 or 2, there is no
>delay.
>
>However, I can see very little reason to
>use instance control 1. In fact, 0 is
>more flexible. With setting 0, you can
>choose if you want to open the file in
>the same or different instance, e.g. by
>using drag and drop. In addition, drag
>and drop works with all files, not just
>with those that have been associated to
>Vedit.

I always use 1, because I rarely use Explorer (which is clumsy), but open files from ZTreeWin.

The delay is often evident, a 2nd instance of Vedit starts, then closes. (I do not remember this behaviour in Win98)