Jump to content
Muxe Inc Forums
Sign in to follow this  
Crimso

Network Disk + Quick-dirs = Error

Recommended Posts

Crimso    0

I have one network disk on which Quick-dirs list works very bad.

After the start of NDN (Windows wersion) I can go into folder on the disk "by hands" and it all looks OK. But if I go into that folder using Quick-dir, whole disk became to be bad.

Command prompt on this disk filled (I think) with garbage, contained some very special symbols and looks like that

... >

When I work in normal panel (say, right) and press Tab to jump into that bad panel (left), cursor jumping to the left panel ... and jump back to the right panel.

If I open "bad" folders in both panels and press Tab - cursor begin to jump between panels eternally.

If I jump into bad panel using mouse - it works ok, and I can navigate between folders of this disk, but command prompt looks equally bad except the root od the disk, where it looks normal ( z:\> )

Disk remains to be "bad" until I restart NDN.

Screen grabber doesn't work if that "bad" prompt is in the area of grabbing (in the printscreen in the end of letter I inserted that line manually)

First time I found it after installing last release (2.31.1909), previous release seems worked OK.

This error appears not at all network disks, but only on one.

 

If you will need more info - I'm ready to give it, just ask me what you need.

 

╔═[1]════ z:\distr\gransmeta\liveupdate ═════════╗╔═══════════════ c:\work\MapRuler ═══════════[]═╗
║                      Name                      ║         Name          │         Name           ║
║..                                              ▒║fAttrArrayMulti.dfm    │fAttrDate.pas           ║
║PlugIns                                         ▒║fAttrCheck.dfm         │fAttrNum.pas            ║
║Reports                                         ▒║fAttrDate.dfm          │fAttrSearch.pas         ║
║Scripts                                         ▒║fAttrNum.dfm           │fAttrString.pas         ║
║                                                ▒║fAttrArrayMulti.pas    │                        ║
║                                                ║fAttrCheck.pas         │                        ║
║───────────────────────────────── 15_766_214/8 ─║║───────────────────────┴─────── 28_292_156/117 ─║
║GranSmeta.chm             429_589  1.09.03 18:05║║SelectGrid.pas              2_535  3.11.06 17:05║
║GranSmeta.chm                                   ║║SelectGrid.pas                                  ║
║         8_355M free bytes on drive Z:          ║║         13_351M free bytes on drive C:         ║
╚[ A C D J N O P S T X Z * ? # : ]═══════════════╝╚[ A C D J N O P S T X Z * ? # : ]═══════════════┘
                                    ...                                >                               
1Left   2Right  3ViwAlt 4EdtAlt 5UsrScr 6RenFas 7FindF  8CmdHis 9Tetris10Video1 BSort   CDrive

Share this post


Link to post
Share on other sites

Hi Crimso.

 

This is really strange.

Of course I would like to have more information, but I don't know what to ask for. :)

The best thing of course would be if you could find the reason why NDN behaves like that.

 

Is "z:\distr\gransmeta\liveupdate" the bad directory?

And it only happens if you change the directory by quickdirs?

 

Can you recreate this error?

If yes, I could try to make a debug version which would save information

on what is wrong when accessing this directory.

 

Stefan / AH

Share this post


Link to post
Share on other sites
Crimso    0
Is "z:\distr\gransmeta\liveupdate" the bad directory?

And it only happens if you change the directory by quickdirs?

 

I have two quick-dirs on this disk, an both of them make the whole disk "bad" when I jump into them by quickdirs.

If I select this dirs manually, not by quickdirs, all working OK.

 

Can you recreate this error?

If yes, I could try to make a debug version which would save information

on what is wrong when accessing this directory.

 

It recreates every time when I jump into that dirs by quickdirs.

 

 

Share this post


Link to post
Share on other sites

Hi again.

 

I have created a simple debugging version for you to test:

http://bnhof.de/~ho1459/temp/ndn_qd_dbg_0w32.rar

 

Do the following, after you installed it to a new directory (not over your original installation):

- add the network disk to your quick dirs

- goto the quick dir the same way as in the old version

- do you see the error again?

- send me the file C:\vp_debug_logfile.txt

 

Thanks for your help,

Stefan / AH

Share this post


Link to post
Share on other sites
Crimso    0
Do the following, after you installed it to a new directory (not over your original installation):

- add the network disk to your quick dirs

- goto the quick dir the same way as in the old version

- do you see the error again?

- send me the file C:\vp_debug_logfile.txt

Yes, error is exists.

Logfile is:

 

_DoChange start

C:\NDNX Z:\DISTR\GRANSMETA\LIVEUPDATE

A

B

z:\distr\gransmeta\liveupdate\.

Z:\DISTR\GRANSMETA\LIVEUPDATE C:\NDNX

_DoChange end

 

 

Share this post


Link to post
Share on other sites

Hello.

 

Unfortunately, I could not see any error, so I extended the error output.

Please try this version and post the results again.

If there are too many files in the listing, please cut the list or upload the file somewhere.

 

http://bnhof.de/~ho1459/temp/ndn_qd_dbg_1_w32.rar

 

Thank you,

Stefan / AH

Share this post


Link to post
Share on other sites
Crimso    0

This time log is

 

_DoChange start

Directoryname: "C:\NDNX" Target: "Z:\DISTR\GRANSMETA\LIVEUPDATE"

A

B

Target: "z:\distr\gransmeta\liveupdate\."

GotoFile start

Directoryname: "Z:\DISTR\GRANSMETA\LIVEUPDATE"

ReadDirectory start

Files:

0 ..

1 PlugIns

2 Reports

3 Scripts

4 Templates

5 files.ini

6 FromErkt.dll

7 GranSmeta.chm

8 gransmeta.exe

9 GranUpdate.dll

10 History.ini

11 import.ini

12 instruction.doc

Directoryname: "Z:\DISTR\GRANSMETA\LIVEUPDATE"

CurrentDirectory: "Z:\DISTR\GRANSMETA\LIVEUPDATE"

ReadDirectory _end

Name: "."

GotoFile end

Directoryname: "Z:\DISTR\GRANSMETA\LIVEUPDATE" OldD: "C:\NDNX"

_DoChange end

 

 

Maybe you are searching in wrong place. Current directory is not damaged, all file operations (copy, compare etc.) works OK. I think something damaged in displaying of prompt (that part of command line that before an '>' sign), it got non-printing characters....

 

 

Share this post


Link to post
Share on other sites

Hello Crimso,

 

it is very possible that I am not searching at the right place in the code.

 

But all I knew from you is that quickdirs behave differently than going into that directory

by "cd" or cursor keys and enter. So, I started searching in the quickdir code.

 

Let's check the command line handling:

http://bnhof.de/~ho1459/temp/ndn_qd_dbg_2_w32.rar

 

Please post the result again.

 

Thank you,

Stefan / AH

Share this post


Link to post
Share on other sites

Hi Crimso,

 

for every drive the current directory is stored in NDN.

It is an array from ['A'..'Z'].

The error was that drive characters were not upcased before

indexing into this array.

z is bad, Z is good.

 

Thank you for your help and bug report,

Stefan / AH

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×