Hi Paul, This may be way off but last week Microsoft unleashed another update. One of my Rbase 2.11 users opened Rbase while the update was proceeding (Microsoft usually sends you that little note saying you can keep working) and she promptly got a NTDVM error that would not go away. We had to use system restore to set the Windows XP back to a day before the update. Once we did that we let the Microsoft update do its thing without opening Rbase until the update was finished and the computer had been rebooted. Everything was fine after that. Regards, Dave Fitts State of Maine
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Bill Eyring Sent: Monday, November 23, 2009 10:51 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: RBase Lockup & NTVDM Errors Paul, It could be a conflict in the computer's path. Try modifying the path by creating a batch file as follows; set savepath=%path% path=c:\rbti\legacy\dos\211 (or whatever directory 7.6 Dos is installed) rbase path=%savepath% exit Also, make sure there is no reference to the old RB5 path. Regards, Bill Eyring ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Paul Hill Sent: Friday, November 20, 2009 9:40 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RBase Lockup & NTVDM Errors We recently upgraded from 4.5DOS to 7.6DOS preliminary to converting to RBase for Windows. Since the upgrade, a number of our workstations lockup wat times displaying an "NTVDM" error message or users are thrown completely out of RBase when attempting to print from Rbase. Any ideas about how this can be resolved would be appreciated. Paul Hill
