C / C++ / MFC

13-Jun-06 5:50

Hi
I have 2 PCs on a network (with shared hard drives, but not mapped). I wish to access the hard drive of Machine_2 from Machine_1 from within my Visual C app - can this be done without mapping the hard drives?

From Machine_1, I have tried opening "\\Machine_2\C\MyFolder\MyFile.txt", but I am unable to locate the file - am I doing something wrong, or this simply cannot be done?

Hope someone out there can help!

Thanks

Mike

David Crow13-Jun-06 6:00

13-Jun-06 6:00

69 Bay wrote:
can this be done without mapping the hard drives?

Certainly, just use UNC.

69 Bay wrote:
From Machine_1, I have tried opening "\\Machine_2\C\MyFolder\MyFile.txt", but I am unable to locate the file - am I doing something wrong, or this simply cannot be done?

What does the actual code snippet look like? Shouldn't that be C$ instead (assuming you are wanting to go through the administrative share)?

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb

69 Bay13-Jun-06 6:11

13-Jun-06 6:11

Thanks for looking

I am experimenting at the moment and using :

FILE *fMyFile;
fMyFile = fopen("\\\\Machine_2\\C\\MyFolder\\MyFile.txt", "r");
if(fMyFile!=NULL)
fclose(fMyFile);

Each time I try this, fMyFile comes back as NULL !

Thanks again
Mike

David Crow13-Jun-06 6:16

13-Jun-06 6:16

69 Bay wrote:
fMyFile = fopen("\\\\Machine_2\\C\\MyFolder\\MyFile.txt", "r");
...
Each time I try this, fMyFile comes back as NULL !

Because you are not using C$ like I mentioned, unless you actually have a share on Machine_2 named C.

What is the value of errno when fopen() fails?

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb

69 Bay13-Jun-06 6:21

Re: accessing a networked hard drive [modified]

13-Jun-06 6:21

Hi
I am a d**khead!

I just realised that the shared hard drive on Machine_2 was not shared as "C", but as "Mikes C"

Changing my app to this has got it working!
Thanks for your help

I will check more thoroughly before asking again!

Mike

bob1697213-Jun-06 6:06

bob16972

13-Jun-06 6:06

If Machine_2 is not "resolveable" then this will fail.

You can put the entry in your "HOSTS" file (Not really ideal)

or

You can put an entry in your domain's DNS server(s) and make sure it is the first DNS server the machines hit and "forward" unresolveable requests to outside DNS servers for those non-intranet thingy's like yahoo.com, msn.com, etc... (preferable for deployments as changing server IP's simply requires a change in the DNS entry at the server(s))

or

put the IP directly in place of the computer name in the UNC path (best for testing)

\\192.168.50.50\C\MyFolder\MyFile.txt

-- modified at 12:09 Tuesday 13th June, 2006

Also, don't forget about the "rights" issues that come into play

69 Bay13-Jun-06 6:22

Re: GetFirstView Position()

13-Jun-06 6:22

GetFirstView Position()

DanYELL13-Jun-06 5:47

DanYELL

13-Jun-06 5:47

I have this:

<br />
POSITION rpPos ;<br />
<br />
rpPos = pDoc->GetFirstViewPosition();<br />
while (rpPos != NULL)<br />
{<br />
   pView = (CView1 *)pDoc->GetNextView(rpPos);<br />
}<br />

How do I know which View I am in? Is there any way
of displaying rpPos and knowing from that which view
I am currently in?

Please, any response any one can give me will be
greatly appreciated.

Sincerely,
Danielle Brina (an overworked graduate student)

led mike13-Jun-06 5:55

led mike

13-Jun-06 5:55

their are several ways, see CObject::IsKindOf(...)

you might consider designing your own solution.

Re: GetFirstView Position()

David Crow13-Jun-06 6:02

Re: GetFirstView Position()

13-Jun-06 6:02

led mike wrote:
you might consider designing your own solution.

How does wanting to know what view is in a list have to do with designing one's own solution?

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb

led mike13-Jun-06 8:55

led mike

13-Jun-06 8:55

I meant eliminate the use of RTTI or CObjects version of it to identify the "type" of "view". My post was not clear at all, my bad.

Problem with termination of a thread

SWDevil13-Jun-06 5:44

SWDevil

13-Jun-06 5:44

Hi,

I have an application, in which I run a thread when the application loads. This thread calls a certain function that initializes an array, and takes a few minutes to run. The thread works good, but if I close the application before the thread is done then there is an assertion.

How can I overcome this? Can I maybe force the thread to end if the user closed the application before it finished?

Justin Tay13-Jun-06 5:56

Justin Tay

13-Jun-06 5:56

Perhaps in your OnClose handler you could have...

ShowWindow(SW_HIDE);
WaitForSingleObject(m_hThread, INFINITE);

led mike13-Jun-06 5:56

led mike

13-Jun-06 5:56

SWDevil wrote:
then there is an assertion.

Is the assertion a Debug only mechanism? What is the behavior in "Release" mode?

David Crow13-Jun-06 6:03

13-Jun-06 6:03

SWDevil wrote:
How can I overcome this?

Read here.

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb

Zac Howland13-Jun-06 6:27

Zac Howland

13-Jun-06 6:27

You will need to do 2 things to do this cleanly:

First, create an event and pass the event to the thread. Each pass of the Thread, use WaitForSingleObject with a low timeout value to see if the thread needs to exit (if it does, do any cleanup you need to and return from the thread).

The first step will allow the thread to exit cleanly. In your main thread, you will need to also add a WaitforSingleObject and use the thread's handle as the object. Use a timeout value appropriate for you (INFINITE is NOT appropriate here as it will deadlock your application's shutdown procedures). If the Wait times out, call TerminateThread with the handle for the thread (this is a forceful killing of the thread).

If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week

Zac