Network service take too long to start

I have an app that runs as the shell program in an XPe system (basically my application has replaced the windows explorer.) At the very beginning of this app, I create a folder which I need to share to a network. So I create the folder and use net share to share it. OK no problem right?. wrong! The server service takes about 30-40 second before it starts, and if I try to use net share before then, I can't see the shared folder on a remote PC (appearently the net share fails). If however I put a delay of 40 second at the beginning of my app, and then create the folder and share it, it works.
Question(s)-
1. Is it normal that the network connection take 30-40 second before establishing?
2. Is there a way I can know if the connection is started?
3. Any comments, questions?
thanks for your time
kevin

We use C++ in login, it is fast!
There are more api call then I can ever think of, get api loader.exe and search it! I think there is one like that. C++ can get to api call with out declaring them.
Good Luck.
:bigyello:

From what I can tell the speed for the network connection isn't dependent on the program. I have an XP pro system here also, an it seems to take the same time for the connection to establish.

bump

if you post your code, i will try it. i have 2 xp systems up for a few more days, then the desktop will be W2K Workststion. I normally map a drive to WS, and haven't experienced noticeable delays, but I don't do it programmatically, and I just wait until it finishes before I write to it.

Quote:

---

if you post your code,

---

I would if I could, but it is all inside the embedded OS. Here is an experiment you might try tho. Connect 2 machines in a LAN. Boot one machine and go to the folder where you would normal "see" the other machine in the network. Then turn the other machine on and measure the time it takes for it to become "visible" to the machine that is already booted. I measured about 35 second after the XP splash screen goes away.
kevin