Okay, so it's not the filesystem, but RB doesn't exploit what the filesystem
allows... perhaps RB makes use of FAT16 or FAT32 api calls...?
Would that make sense as a possible explanation? Of course, RB should clean
up its own mess after itself, so it's as worthless an excuse as it gets. So,
I'll take it there's another explanation.
Ronald Vogelaar
--
http://www.rovosoft.com
----- Original Message -----
From: "Fargo Holiday" <[EMAIL PROTECTED]>
To: "REALbasic NUG" <[email protected]>
Sent: Sunday, September 10, 2006 6:53 PM
Subject: Re: RB hangs when trying to run or build & Solution to this problem
NTFS doesn't have that limit on number of files. FAT16 had that issue, and
even though it was corrected in FAT32, Windows never really caught up to
it so you'll often see issues even on FAT32 systems.
http://www.ntfs.com/ntfs_vs_fat.htm
Thought I'd toss that in there.
Ronald Vogelaar wrote:
Fellow list members,
Today, I encountered a problem that had me scratching my head for a
while. With a shot of luck I quickly found a solution though.
While I was working on my Metropolis project, I suddenly found that RB
(on Windows) would no longer build or run my project. RB would hang and
could only be terminated by means of the task manager. Smaller projects
would run and build without a problem though.
I went back from r3 to r2, but the problem persisted. Rebooting my pc
(which I rarely do) did not solve this either.
I then went looking and found that the directory c:\Documents and
Settings\MyUname\Local Settings\Temp contained over 65000 files; by the
looks of it almost all of them 0 byte temporary files.
I deleted all of them and voilá, RB would run and build my project again.
I then found out that RB creates 79 new 0 byte temporary files on each
consecutive run. So, on the second run there were 158, and so on.
My guess is that my system was bumping into the file system (NTFS) limit
of maximum number of files that a single directory can hold.
Perhaps RB creates fewer files on smaller projects, which would explain
why those would still run (79 were too many, but there was room for a
smaller number).
So, if you're on Windows, you might want to check out that particular
directory and do a bit of cleaning up before you hit the ceiling in the
way that I did. I suspect that this would also prevent you from
installing new software on your pc, as installers often write to this
same directory, plus a myriad of other problems could occur with any part
of the OS or other software accessing a directory with that many files.
I have no time to file bug reports, so if anyone would feel so inclined,
or if RS could follow up on this problem directly, this would be
appreciated.
Ronald Vogelaar
--
http://www.rovosoft.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
