NAM : DISK IS FULL

Wow Seriously ??? This is the first time I don't get an answer ..

Well anyways, i'm onsite now, going through the harddrive, doing a chkdsk, erasing large log files etc ...

Maybe corruption!

Re-install and see if fixes.

Maybe there is a problem with OS2, try going there and see if something is up.

Thanks Curlycord .. I'm worried about file corruption as well. I did a chkdsk, and it found a couple minor errors but didn't free up any space. I ended up finding a folder Called WILLY (I don't know what that is) that had many files in them, however 1 of them called download.zip that was 400mbs, and another download.zak that was also about 400 mbs... I erased them both, and now there's over 800mb's free space.

I'm hoping this will solve it for good. (Considering entire backups of systems and their messages fit on a few floppy disks, i'm assuming 800mb's free space now will be plenty)

I turned off logging just in case. I don't really use them anyways.

Willy huh!

That was a script put in by Telus... a major telco here in Canada.
If anyone gets a complaint by a customer stating there main greeting changed on it's own and is now a message for a different company like a bank then Willy might be the culprit!

Thanks for that info curlycord. That would make sense since I'm in Montreal and this was a refurb system when bought.

Do you know if there's any harm in simply erasing the entire directory and all it's contents, since I know they don't use Telus's services when it comes to the phone system ?

I cannot say for sure, my guess is delete it but if my info is not correct then I look bad and your screwed hehe.

hehehehe... well I left the directory there and just deleted those 2 huge 400mb files download.zip and download.zak

Thanks

2 days after I did this the 800mb's I free'd where gone and they were getting the same "disk is full" error. We ended up re-installing everything on the harddrive from scratch. It didn't even let me backup the NAM first (Would always Abort) so I had to reprogram everything.

My supplier is stumped, he has no clue was happened.
Obviously SOMETHING was eating up any and all space on the hard drive.

I haven't seen this error in quite a while, but as I recall I ended up doing the same thing you did. I am guessing that it was a data corruption or cross-linked files.

Brian Cox