User forums > Using Code::Blocks

No access to Samba share

<< < (2/3) > >>

BlueHazzard:
This image does not help...

Can you create a .cbp file with the notepad with exact the same path as codeblocks would?
Can you create a text file on the share and rename it from Test.txt to test.cbp  (you have to enable the show extension option in the folder settings for this)?
Can you create folders with the explorer on the share?
Can you create a project locally?
Can you copy the local project to the share and use it in codeblocks from there?

Does codeblocks runs as a other user?

It makes no sens that you can create folders/files with the explorer but not create files with codeblocks...
Things i can think of:
1) Special characters (all non ascii characters or space) in the path/project name
2) You don't have write access on the network drive
3) You don't have permission to create folders on the network drive
4) You don't have permission to create special files (for ex. files with the cpp or cbp file endings) (this would be very strange)
5) Your anti virus or firewall is blocking codeblocks

gilada:
Can you create a .cbp file with the notepad with exact the same path as codeblocks would? YES
Can you create a text file on the share and rename it from Test.txt to test.cbp  (you have to enable the show extension option in the folder settings for this)? YES
Can you create folders with the explorer on the share? YES
Can you create a project locally? YES
Can you copy the local project to the share and use it in codeblocks from there? YES works even build and run (cout output changed)
Does codeblocks runs as a other user? NO

The points 1 to 5;
1. no
2. no
3. no (via Explorer no problem)
4. has what, how can I check this
5. my firewall / antivirus is AVG, I inserted a registration for codeblock.exe there.

Do next tomorrow, for example: mapping

gilada:
Disable firewall and AVG, problem remains. It is not even time

Was the share mapped (X:), and behold codeblocks creates a new project and build run works too. Thus one can come out.

However, it should be mentioned that working codeblocks on linux without mapping.  ;)

sodev:
Well, i guess the problem was that you tried to access your project directly through an UNC path. This cant be done with standard c++ or wxWidgets without using specially crafted path names that CodeBlocks apparently doesnt use.

However using a regular path, something with a drive letter, does, so thats why you could fix it this way. Technically you also have a "mapping" on linux, basically everything is mapped there on a regular path in the filesystem so you dont have these issues there. You can access pretty much everything with regular paths, no special handling necessary there ;).

gilada:
Working codeblocks with the UNC path (Win7)? If Yes, what needs to be done.

Navigation

[0] Message Index

[#] Next page

[*] Previous page