I am confused as to what exactly qualifies as Windows 'use'? The Win '95 machine I cited does the following everyday except Sunday (I forgot I added a task for early Saturday!) via an application written in Visual Basic 6.0: o Queries the serial port twice a day to correct the system clock. (On the serial port is an embedded processor that works with an active GPS receiver.) o Reads system time 3 times a second and runs through a list of times to start/stop MCI audio record VB control. o Soundblaster visual LED VU meter. Runs and is updated anytime audio control ddoes not have possession of the SB card. o Windows drive-share daemon. Allows access to recorded files for transfer off the 'record' platform. The recorded audio files (about 6 total) total about 180 MB each weekday, about 200 MB on Saturdays. o Every day, or every two days, or at week intervals sometimes I access Windows Explorer to delete accumulated files. So, I see you want to qualify it as 'interactive use' with an operator, brining up and down apps - would this not then open up the possibility that the various apps that one uses are at fault and not 'Windows' per se? I can see where memory allocate and de-alocate then becomes an issue ... RF Jim ----- Original Message ----- From: "Herbert Graf" To: Sent: Wednesday, September 11, 2002 10:55 AM Subject: Re: [OT]: Fitting Win2k onto embed-->current Win 95 experience > > "... however for 9x stuff (95, 98, Me) it doesn't > > matter WHAT you do, they are inherently flawed and > > will crashed if used." > > > > Perhaps that has been/was *your* specific experience (perhaps bad, > > colored, faded memory?), but that is not what all of us experience! > > > > In several, no, make that *almost 5 years* of daily use > > (since 1997) on a Monday thru Friday basis running an audio > > application that records three hours of audio program material. > > I also have win95 boxes running for weeks without a crash, you didn't read > what you quoted: "if used.". Win95 is perfectly stable if you start it and > leave it, however if you start a program, close it, start another, close it, > start another continuously win9x doesn't last long, a day or two at most. > The flawed nature of win9x has partially to do with recouping resources (it > also has other flaws that I won't get in to), if you start one program and > let it run you don't have anything to worry about (as long as nothing else > is starting and stopping and your program is written well). TTYL > > -- > http://www.piclist.com hint: The PICList is archived three different > ways. See http://www.piclist.com/#archives for details. > > -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details.