|OK had a nice sleep, and I thought based on my confusion I would write down some more information in a word document to help me sort out my logic so here is what I wrote a while ago!|
I am getting confused so decided to write it down to try and get this straight in my mind!
As was said their is not much information about my system so here goes :)
First off I realised I have a network problem, PC2 is not able to send files to PC1 unless the second network adapter on pc1 is enabled. I disabled it because it was the cause of internet drop outs, as the primary adapter on pc1 is not allowing incoming from other pc's on the network this poses a problem. My original objective on pc1, was to optimise speed by having 1 network adapter for Internet traffic only and the 2nd adapter on pc1 for Local Area Traffic only!
Some times the above works! The 2 network adapter's are NOT bridged and I do not know how to do this or if I want too, my aim was to isolate Internet traffic on my Local Network for data security from being hacked.
Problem windows 2000 on pc1 often swaps network adapters and tries to use the wrong one for Internet traffic, the one which points to pc2's IP and not the router, = No Internet access)
PC2 however has only one network card at the moment, I have another I am thinking of fitting for redundancy and to perhaps sort the problem but need help with that.
2/ Batch files, I figured out why the STATFLAG is not working, pc2 is not able to write the statflag to pc1 so we need a slight rethink.
3/ Basically PC1 needs to manage it's own statflag which PC2 can never reliably touch until my network is sorted out! PC1 can however always access PC2 via this Network card used for the internet, so clearly I have not got the Internet and LAN separated yet, if I try to set PC2's Network to use PC1 for LAN traffic I get Internet drop outs not sure why this is? Anyway those are my problems explained with the network.
COMMENT TO SELF! TO GET THIS RIGHT IN MY HEAD:
*** LOGIC ***
a) PC1: When a-attrib files ready, check PC2 ready (Base on 10 Minute Ready FLAG at PC2)
b) If PC2 Ready, PC1-copy files to PC2, Else PC1 loop's 30 Second wait cycles ; Until PC2 Ready
c) PC2 (10m Flag Exist) PC1 copy's Files PC2, (remove (a) attribute from files copied )
d) PC1 sets (File's Copied flag) ON PC2 so PC2-Knows files are waiting!
e) PC2 lookfor.bat sorts files in directories, when done removes: PC1-(File's Copied flag)
f) PC2 lookfor.bat goes into a 30 second loop looking for (File's Copied flag) made by PC1
f) PC1 starts again from a) above
Another thing I need to mention is PC1/2 = my actual real computer name as known over the Network.
I think we really need 2 flags a rdyflag for 10 minute ready status flag, this can be deleted at boot time by flag bat as the first job, before RECREATING a new one after 10 minutes.
One of the things that confuse me is that we seem to be using only one flag, and there are 2 situations 1 is that PC2 is up for 10 minutes, and 2 that files are ready to be sorted so if we had a flag for each purpose I will not be so confused :p
2nd a statflag made when files are ready to be sorted ! Called: srtflag
rdyflag flag being needed before PC1 sends files across ….
I think storing most flags in a special folder on \\PC2\stat\* locally> as G:\migrate\stat\rdyflag
on pc2 would be best, as both PC1 & 2 can access these folders, PC1 only needs to create a local flag for itself if PC2 is off-line.
I hope I have managed to get this all right ?