Filenames with all caps crash new installation of 4.5

[scampisi]

i am trying to install Sugar Suite 4.5 for the first time. I just downloaded it and then ftp'd it up to my apache server running version 4.4. When I go to the directory, I merely saw a list of files . . . nothing ran. I noticed that there was an index.php file, but it's filename was in all caps. I renamed it from INDEX.PHP to index.php and then sent my browser to the directory again. This time, there was an error message that said it couldn't find install.php. I looked and there was a file named INSTALL.PHP. I renamed it to install.php and then proceeded to the next error.
I looked and about 20 of the files in the root directory of sugarsuite were in all caps. I noticed that the other folders were also in all caps.
I thought my FTP program my have somehow created this issue, so I tried it with another FTP program with the same results. Is there something I'm missing? Are these filenames supposed to be ALL CAPS?

thanks for any help.

[kpit]

Details about your system should be posted to get a decent response. Look at http://www.sugarcrm.com/forums/showthread.php?t=10986

[scampisi]

Oddly enough, I DID read the suggested URL before I posted.

1. I did a thorough search of the forum for installation problems related to filenames being in ALL CAPS
2. I then started a new thread and was careful about wording my title to give details of the problem for those reviewing the newest posts
3. I described the issue and gave as much info as I thought was pertinent. I omitted the MYSQL version and PHP version but I don't see how they come into play when the file is NOT even being parsed yet. The filenames are ALL CAPS! The version of Sugar Suite, I listed as 4.5 instead of the more verbose 4.5.0b, but I did point out that I had JUST DOWNLOADED IT so that it would be clear that it was the latest version. I didn't think a list of steps "to reproduce" was necessary, since all I did was download it and FTP it up. I didn't NUMBER these steps, an error that I profusely apologize for.
4. I WILL post a response once it is finished

I have fixed the problem, and If anyone has the same issue, feel free to PM me and I'll tell what the deal was. A very interesting problem.