I've got problems, need some quick help. - Fixed - Solution enclosed

[IJump]

Ok here is the quick and dirty....

My login script had flaws, the installed rc5 client is not working for some reason.

Here are my questions:

Can I install over top of the existing client without any problems?

If I installed as a service the first time, will reinstalling try to start a second instance of the service?

If I need to remove the client and start over (which might be the easiest at this point), what happens to the work units that are buffered on that machine? Do I need to save those? If so, what is the best way to do that?

OMG! This is so messed up!!!

Moral of this little story.....Stick with the tried and true floppy.

 

[Dantoo]

Don't Panic (in large and friendly letters)

You are Borg as I recall, therefore there is no fear!

The client can be reinstalled over the top without probs in Windows but I can't provide any advice on other OS's. You can simply replace the old files with the new.

Q2 is beyond my ability but I would go the -uninstall option then install again to be safe, but somebody will be along to correct this advice shortly.
Q3 ditto above.
Q4 just save the buff-in and buff-out files to a separate folder and then just put them back into your RC5 folder after you have reinstalled (assuming that you intend to nuke the original folder).

I hope there has been some help in this - if not, somebody that knows what they're doing will come past shortly.

 

[Proxy71]

Can I install over top of the existing client without any problems?
- you can copy one client over an other thats no problem, but you'll have to shut down the client first with the command dnetc -shutdown, then copy the new file(s) and windows will start the "new" cow as a service once you reboot

If I installed as a service the first time, will reinstalling try to start a second instance of the service?
- when you install it as an service that cow will aways want to start.... once one instance runs you can not start another one.... if you want full control over your cow again you will need to remove it as a service or make it visible with the command dnetc -noquiet

If I need to remove the client and start over (which might be the easiest at this point), what happens to the work units that are buffered on that machine? Do I need to save those? If so, what is the best way to do that?

- you can (as mentoined above) just make a copy of you're buffer files and they will be fine once you put them back

OMG! This is so messed up!!!
- no it isn't


hope this helps

 

[Adul]

If you can pass command to the dnetc.exe try this.

Dnetc -shutdown
this will stop the client running. The next thing you do is just copy the client over it.
the proceed with dnetc -svcstart to restart the service.

 

[IJump]

Thanks for the help so far.

I failed to mention that there are two sets of buffer files on some machines. I had someone helping me install and he was installing to a different folder. What is the best way to handle the multiple buffer files?

 

[Dantoo]

Just rename them and save them to a floppy/folder as 1buff-out 2buff-out etc. When you wish to use/dump then change them back one at a time.


Hey Adul, shouldn't you be in bed? Oh it's me that should be - past midnight here!

 

[Adul]

Actually I am at work dantoo.

 

[Ken g6]

The best way to handle multiple buff-in files is to consolidate them with "dnetc -import". I'm not sure, but I believe it works with buff-out files, too. "dnetc -help" gives a terse description.

This may be a stupid question, but on your login script, did you run "dnetc -svcstart" as well as "dnetc -install"? It won't hurt to run "-install" every login; you'll just keep re-writing the same registry key over and over. But unless I'm mistaken about WinNT systems, the client won't run until a reboot or "-svcstart".

 

[Russ]

<< What is the best way to handle the multiple buffer files? >>



As part of the script, you can flush the extra and then delete the install.

cd <directory name>
dnetc.exe -flush
cd\
deltree <directory name>

That's DOS talk, of course, so if you're using some kind if fancy geek language you'll have to convert. You get the idea, though.

Also, Ken_g6 is correct. On any Win32 machine, you need to use the -svcstart switch or reboot after a -install.

Russ, NCNE

 

[IJump]

I have both switches, I have written a high tech dos batch file that flushes from both directories(I think), stops the service, then copies the buffer files out of the one I am deleting, deletes the bad on, then reinstalls on top of the good directory. I think this will work. Wish me luck.


And thanks for all of the help.

 

[IJump]

OK. Here is what I ended up doing. Just in case someone else gets in a similar mess. Created the following batch file(named fix.bat):

c:\windows\dnetc\dnetc -flush
c:\rc5\dnetc -flush
pause
c:\windows\dnetc\dnetc -shutdown
c:\rc5\dnetc -shutdown
c:\windows\dnetc\dnetc -uninstall
c:\rc5\dnetc -uninstall
pause
md c:\buffers
copy c:\windows\dnetc\*.rc5 c:\buffers
deltree c:\windows\dnetc
if exist c:\rc5\dnetc.exe goto :files
md c:\rc5
:files
copy *.* c:\rc5
c:\rc5\dnetc -install
c:\rc5\dnetc -svcstart
c:\rc5\dnetc -import c:\buffers\buff-in.rc5
deltree c:\buffers

A few of the duplicated lines are there in case the client wasn't installed in the first location. The pauses are so I could make sure I knew what was going on in hte event there were problems. It seemed to work great, thanks to the collective brain-power of everyone.