[RBASE-L] - RE: Virtual Memory Problems, RB65++, Win2K

[Gunnar Ekblad]

Mike! I will stick my neck out! I can not replicate in COMCOMP but I belive I can replicate in a one table DB with one commandfile I have a bad betting reputation I already lost 10 Euros to Razzak when I thought I was right, truth is Razzak was right. I bet an other 10 Euros to whatever RBTI are collecting to as welfare that Stephen shortly will reply that Denis UDF solved his problem to!     Besides I must be double stupid since I still don’t se how to manipulate to the Auto options. Which desktop shortcut! Mike if you answer this please send the bill to Mr Bill Gates Somewhere on the northwestcost in US.         Gunnar Ekblad   -----Ursprungligt meddelande----- Fr�n: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] F�r Mike Willochell Skickat: den 14 november 2003 18:56 Till: RBASE-L Mailing List �mne: [RBASE-L] - RE: Virtual Memory Problems, RB65++, Win2K   Dear Gunnar; At 06:16 PM 11/14/2003 +0100, Gunnar Ekblad wrote: 1.      I have no intention to argue with you I don't think that anyone intends on arguing whether the situation exists or not in certain environments. Our real problem is creating an environment and set of circumstances which will recreate the problem on any Windows 2000 machine. All we can do is report what happens on our machines, and until one of us finds the missing piece to the puzzle, there is little that we at RBTI can do. 1.      The problem is real This is very possible. However, based on the examples and details sent to us by several reputable developers, including Mr. McGrath, we are unable to see this problem happen. 1.      In my case the problem is related to LOOPS and zip cmd /c copy within the loop In any WHILE loop that has the ZIP command imbedded? 1.      I can not replicate it in Concomp This is instrumental because it is many times difficult and impractical to send your specific database(s) and applications. Also, this helps us to rule out database design issues and corruption. 1.       Dennis UDF has now for 3 months cleared me from the problem and I stay happy with this workaround 2.      I was not clever enough after right click on NTVDM.EXE to set anything to Auto????!! You actually need to right-click the Desktop Shortcut Icon and go into the Properties. On the Memory tab, you will see many options. See if anyone can create an example for us to test so that we can make the problem visible to our developers. This is the only way that we'll squash this bug once and for all. Thanks. Mike