Hi Robert,
...since you're talking about WSeB being installed - is it HPFS386 or the "usual" one, that you are running?
Sorry if you already told and I simply missed out on it...
Cheers,
Thomas
Hi Thomas...
The two machines I am having problems with are both HPFS as it came with eCS. No driver updates or changes from the default v1.2MR install.
The WSeB machines were running HPFS as originally came with WSeB CP2 PF and didnt exhibit this issue - but are now running HPFS386 v14.039 (if memory serves) and still not showing these issues. I brought that up in response to Saijin to try to say that I hadnt seen this issue until the eCS installs (ie: not on the WSeB machines here). Which also probably wasnt relevant - because the hardware is vastly different.
Sorry to have confused the issue. Was really tired after a very long day when I started this thread.
The only thing I can think of is a flag for the IDE drivers that should - or should not - be set. I think the Intel machine is/was just a failing drive. I've replaced the drive, xCopy'd the C partition back, restarted numerous times without needing to run a chkdsk on Drive D. I may power it off and see if it chkdsk's it properly later.
So... that leaves me with the client's machine. My suspicions are based off the fact that the CD (while using a very default set of parameters for DaniS506) will complete chkdsk properly - but it wont during boot. Those suspicions could be totally wrong though - and the machine isnt here for me to check what's in the config.sys file.
Fortunately, unless they have a big power failure, it doesnt matter (yet).
We've got 3 other boxes installed, same version of eCS, same or similar hard drives, same partitioning - but different motherboards in each... which dont show this problem. Two of them have been running for a couple years now, with only occassional reboots for database/support dll updates (worked our way up from MySQL 3.23.50/RxSQL - to v5 and the RxSQL that uses it).
I think what I need to do - unless someone else has had a similar problem - is make a trip out there and see how the IDE drivers are configured.
(I only posted without that info, because I thought the Intel machine here had a similar problem and I could have checked that here - but I am really thinking it was a bad drive).
Robert
Of course, you call can wait till I am more awake and try to re-state this in a fashion that actually makes sense...
