DHES

Omno, If you're going to address me personally, it would be a good idea to actually spell my name correctly. Well in a nutshell - nobody really understands why the data may have been corrupted (from what I've seen here in this thread), the details of the corruption are rather hazy also. Well, as I ...

The problem The file corruption may not have existed within DHPOS, although it is possible - especially when running beta copies. This is why EVERY single time Dale posts a new update - he reminds people to backup the whole POS folder, data and program files. I'm confused, seeing as I downloaded a ...

There is, however, another benefit to using FAT or FAT32 on your server, even if it is NT based and capable of using NTFS. You can boot off a floppy and read FAT formatted drives, while you have to have a working OS to get to them if they are NTFS. This is big benefit when you consider all your sal...

Thanks all for your suggestions. As I suspected it had nothing to do with the protocol, the file system, the server platform (rather the lack thereof), 8.3 file names or anything with the network. It turned out that for some reason the POS software had corrupted its own file. I launched the global c...

Yes, the response above was from me. The forum logged me out for no particular reason :-(

After searching the archive for win98, path, network, I'm none the wiser, so perhaps I'm trying to solve a non-problem. New installation of POS 6.10, revised 7-28-04. Three machines each running Win98SE. Network is operational with TCP/IP as the only protocol. One (back-office) machine is giving out...