Found this... http://support.microsoft.com/default.aspx?scid=kb;en-us;110845
It looks like the culprit Dll is an old foxpro dll...
Still digging..
I have another theory... Sometimes, and I think this is the case here.. when on of
our network people here sets up users machines, they just copy existing desktop
shortcuts off to the network for a person and then copy them back on their new
machine. If this user had a Win98 machine and just went to a 2000 machine then
Windows might be trying to run RBase as an older program...
Just a thought..
Will get time day-after-tommorrow to research. I have to go to one of our subsidiary
companies tommorrow.
Thanks for the thread of thoughts and directions Jim
MikeB wrote:
The DLL doesn't just load itself. It's being called by something.
----- Original Message ----- From: "Jim Limburg" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, April 01, 2003 3:44 PM Subject: [RBASE-L] - Re: Error starting Rbg65 executable
Renaming it won't be advisable if their other program requires it.I
--Yes, I know, but if it works I going that road. I have done this in the past and no other of our programs have bucked or jumped.
highlight it and End Task/End Process
--I don't think the user needs to mess in this area, although this particular user is capable
do a clean boot and then start RBase first, do you still get the error?
--User said first program she ran this morning was RBase. I am using shortcuts to RBase that run a dat file to startup rbase. Thinking here... I wonder if I should look to see what program the dat extension is mapped to... hmmmm... According to user, she has not installed any new software lately with the exception of MS updates, maybe this is the culprite ???
I have seen this on three different users at our main headquarters, with the person in whom is currently having the problem again being the first person I ever saw this on. At that time, what I could find suggested renaming the Dll, and so I did, and found that to be the answer then.
I have found out that this user does not use Peachtree, nor does she have Quickbooks installed at this time.
Still looking Jim Limburg
MikeB wrote:
Renaming it won't be advisable if their other program requires it. What
use)was saying, is some software doesn't shutdown properly (tidy up after
theand remnants of it can remain in memory (again Ctrl-Alt-Delete and check
RBase.task/process list for the W32sys.dll). If it is is in the Task/Process
list, highlight it and End Task/End Process the item and then start
theBTW, if you do a clean boot and then start RBase first, do you still get
listerror?
----- Original Message ----- From: "Jim Limburg" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, April 01, 2003 3:09 PM Subject: [RBASE-L] - Re: Error starting Rbg65 executable
Thanks Mikefind
I believe this particular user is using Peachtree.. will have to check. I know they are using Quickbooks. I will have them to rename it again and see if anything else breaks..
Crossing fingers Jim Limburg
MikeB wrote:
Google. W32sys.dll is not a part of Windows 32 above windows 3.1. I
init used in a number of software packages including Peachtree Simply Accounting and WINE (a windows environment on Unix/Linux).
If you are running NT (as your email suggests) is the W32Sys showing up
othertask manager as a process that is possibly hungover from running some
software before you start RBase. If it is, remove it from the task
longand
ansee if the error is gone when you start RBase. In any event, it is not
RBase problem.
----- Original Message ----- From: "Jim Limburg" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, April 01, 2003 10:48 AM Subject: [RBASE-L] - Error starting Rbg65 executable
G-Day all
I think I have posted this before without ever getting a responce a
Windowstime
ago. I am going to try again, cause it just became and issue again.version.
One of my users gets this error when she starts RBase Win65 - current
The Application or DLL C:\WINNT\System32\W32SYS.DLL is not a valid
andimage. Please check this against your installation diskette.
Has anyone found a reason for this. I can rename the Dll or delete it
errorthe error goes away, but I am doing this on a user who has had this
DLL,before
and apparently she has some software or ??? that keeps instaling this
so
I don't feel comfortable in the rename/delete solution any more.
Any help appreciated.
Jim Limburg

