Server Not Started

  • Thread starter Thread starter Mule Skinner
  • Start date Start date
M

Mule Skinner

My application (W32) has been running just fine on an image for several
weeks. With no changes made, I started getting this after bootup. It's
occurring right after my RUN Key starts the share.bat file.

On Boot, a CMD Window Opens and shows the following:
Net Share c=c:
the Server Service is not started yet, do you wish to start it? <Y/N> [Y]

and then my application bombs out.

Any reason that this started happening? Any ways to avoid it?
Richard
 
This is weird, If I set my Geode GX1-300 's "General" Bios to:
Disable "Show Delete for Setup" on Boot
Don't show Config Box on Boot

then My shareit batch file seems to run before Server Service is started.
Turning it back on allows it to work. Now what the heck does that have to
do with the timing of Server Sevices? That shouldn't do anything except
save a second or two on boot time and post.

That tells me that the RUN key may run an application before the shell or
server is ready for it and the timing is so close that I get lucky most of
the time and sometimes I don't.

I sure "can't" duplicate tat on an XP Pro machine. Do you think in the next
Service Pack that Microsoft can tweak a few things when it comes to Custom
Shells and Run / Run Once Keys so the Server is actually ready when these
events occur?

Am I off base here?

Richard
 
Hi Skinner,

It looks like some kind of resources has been corrupt.Could it be a
registry (hope so) or could it be some dependency file ,stopping the
service that your applicaiton needs ..you may need to track it.
Make sure that the problem is not with the app .Check whether the app
works fine over a xp / KM's xp pro emulation and does it behave like
the same.
If it doesn't then should be time to investigate.

Regards,
Kesavan
 
Richard,

I have encountered the same problem in scripted NET USE commands. I
think it happens because Windows gives control to RUN key scripts
before all services are initialized. I added a pause (sleep.exe)
command and tuned it down to 30 or 40 seconds -- i.e. whatever worked.

HTH, Roy
 
So you wrote a small program that sleeps for so long and you have your batch
file call it, or does your sleep program call the batch file after sleeping?

Roy Hodgkinson said:
Richard,

I have encountered the same problem in scripted NET USE commands. I
think it happens because Windows gives control to RUN key scripts
before all services are initialized. I added a pause (sleep.exe)
command and tuned it down to 30 or 40 seconds -- i.e. whatever worked.

HTH, Roy

"Mule Skinner" <[email protected]> wrote in message
My application (W32) has been running just fine on an image for several
weeks. With no changes made, I started getting this after bootup. It's
occurring right after my RUN Key starts the share.bat file.

On Boot, a CMD Window Opens and shows the following:
Net Share c=c:
the Server Service is not started yet, do you wish to start it? <Y/N> [Y]

and then my application bombs out.

Any reason that this started happening? Any ways to avoid it?
Richard
 
Richard,

I call sleep.exe within my batch script. Its a DOS command utility
that accepts the number of seconds to sleep as a parameter and returns
control to the batch file after that time elapses. Of course, you can
use whatever timer pause/wait utility you have available in your
scripting language. If you want a copy of sleep.exe, e-mail me
off-line since the Google NG engine doesn't give me the option to
attach a file here.

Roy


Richard said:
So you wrote a small program that sleeps for so long and you have your batch
file call it, or does your sleep program call the batch file after sleeping?

Roy Hodgkinson said:
Richard,

I have encountered the same problem in scripted NET USE commands. I
think it happens because Windows gives control to RUN key scripts
before all services are initialized. I added a pause (sleep.exe)
command and tuned it down to 30 or 40 seconds -- i.e. whatever worked.

HTH, Roy

"Mule Skinner" <[email protected]> wrote in message
My application (W32) has been running just fine on an image for several
weeks. With no changes made, I started getting this after bootup. It's
occurring right after my RUN Key starts the share.bat file.

On Boot, a CMD Window Opens and shows the following:
Net Share c=c:
the Server Service is not started yet, do you wish to start it? <Y/N> [Y]

and then my application bombs out.

Any reason that this started happening? Any ways to avoid it?
Richard
 
Back
Top