4coder»Forums
plb
9 posts
4coder can't open files on a network mapped drive
Edited by plb on Reason: Initial post
I have a usb drive attached to my router and mapped to Z: on Windows. If I try to get 4coder to open a file there from the command line it pops up without having loaded anything. If I then ctrl-o to try to open a file in that directory, the listing is empty. I can pull these files up with other text editors, so it seems to be a 4coder specific issue. There also isn't a problem in particular with the files themselves and 4coder, if I copy them to my c:\ they open just fine.

I also have setup a file association in Windows so that I can double-click a .cpp or whatever file and it automatically launches in 4coder. This works fine for files on the C: drive, but with the network drive, I see 4coder flash on screen for an instant and then disappear.

Windows Event Viewer shows two entries that seem to correspond to these failures (see below). I have the .wer file handy if you'd like me to submit it.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
Fault bucket 1543837729943311864, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: 4ed.exe
P2: 0.0.0.0
P3: 5af080b1
P4: 4ed_app.dll
P5: 0.0.0.0
P6: 5af080b0
P7: c0000005
P8: 000000000001dd08
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREEB3.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREEF2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF03.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF09.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF1A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_4ed.exe_e359e8998b2ec537cc3477c167f6dc065ec2332_d2208193_3ff2f182

Analysis symbol: 
Rechecking for solution: 0
Report Id: ff2b62a9-ca41-4a9f-a85d-e456ec07f6f3
Report Status: 268435456
Hashed bucket: 3ba1cf3a4b0ea068256cd03c5c1dd5f8
Cab Guid: 0


 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
Faulting application name: 4ed.exe, version: 0.0.0.0, time stamp: 0x5af080b1
Faulting module name: 4ed_app.dll, version: 0.0.0.0, time stamp: 0x5af080b0
Exception code: 0xc0000005
Fault offset: 0x000000000001dd08
Faulting process id: 0x3320
Faulting application start time: 0x01d3f93e7e709440
Faulting application path: C:\4coder\4ed.exe
Faulting module path: C:\4coder\4ed_app.dll
Report Id: ff2b62a9-ca41-4a9f-a85d-e456ec07f6f3
Faulting package full name: 
Faulting package-relative application ID: 


Allen Webster
476 posts / 6 projects
Heyo
4coder can't open files on a network mapped drive
Yeah this is a known issue, 4coder just fails to look at a network drive. I need to set up a network drive to test still so I can test it and figure it out.