ColdFusion Builder with case sensitive file system on Mac?

Hi there,
I tried to install CF Builder on my MacBook Pro (Intel), OS-X 10.5.7 with case sensitive file system. Installation went smoothly, but, when I try to launch CF Builder, I get an error saying that the "architecture is not supported". Is it just nor possible to have CF Builder on a case sensitive fs?
Thank you
Chris

I am having the same issue and logged in here to see what the deal is.
After I installed cfbuilder my flex builder crapped out as well.
The cfbuilder logs (which were conveniently scattered throughout my system for no reason) report that I am running:
java.vm.version == 1.5.0_19-137
But if I run "java -version" in terminal I get:
daves-macbook-pro-2:~ Dave$ java -version
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03-211)
Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02-83, mixed mode)
"Is JDK 1.5 available in the system"
Definale "available"...
Does it exist? yes
Is it set to default? no

Similar Messages

CS5.5 Master Collection on Case-Sensitive File System

Hello,
The first thing I'll say is that I already know it's not possible to install on a case-sensitive file system.
So, on to my question. I have been tasked to find out a way to get this installed on our 30-35 Macs with case-sensitive file systems (required for other courses/tasks, so not an option to format.) I was trying to think of a work-around that would let me install and use the CS5.5 Master Collection, but have not been successful yet. Please note, I am not looking for a hack or extensive renaming of a bunch of files or other half-solutions I've found.
Basically, what I was wondering is, if I go into Disk Utility and create a 35GB "Disk Image", mount that, and then try to install, why doesn't that work? I mean, I am technically trying to install to a case-insensitive file system at that point, but CS5.5 still pops up with an error. Has anyone gotten this type of solution to work, or any other for that matter? Luckily my college hasn't bought the licenses for all these systems yet, but when a solution is found, they're jumping on it right away. The main reason I don't want a "hacky" solution is that being deployed on 30-35 systems, this has to be a simple solution, not something that takes hours per system.
Any insight is greatly appreciated.
Jeffrey Simmons

Thank you for the information, I had a hunch it was installing stuff elsewhere too, but wasn't 100% sure. As for the problem, I ended up just converting to a case-insensitive boot partition. To others who may want to do this, I used iPartition without a problem. The only catch is, you can't just run it from the OS drive, you either have to burn a iPartition Boot DVD (requires you have your OS dvd as well), or do what I did and just install OSX to an external drive, install iPartition, then convert the file system on the regular OS drive. A bit of a hassle, but you don't have to format your system.
CS5.5 Master Collection then installed fine, with no problems. Unfortunately, Photoshop keeps repeatedly crashing. It's fine for hours, then crashes 4+ times within an hour. Repeats this over and over unfortunately. Adobe support hasn't been helpful at all, so I'm just going to return this software and continue using Gimp. It has always done everything I wanted, but I wanted the "name brand" software. In the end, it's not worth the hassle, and definitely not worth losing my work over and over, so back to the store it goes. Thanks again for taking the time to help out though.
Jeffrey Simmons

Case-Sensitive File System?

I downloaded the trial for Flash CS4 pro and it won't install on my computer.
It says:
System Requirements Error
This software cannot be installed because the file system of the OS volume is not supported. The OS volume should be local , writable and should have non case-sensitive file system
Anything I can do to get it to work? I have a MBP running Leopard on an intel processor.
Message was edited by: guynjoan

guynjoan wrote:
The hard drive is internal. And Adobe tech doesn't work on the weekends. I checked the "get info" on my hd and it said it is case-sensitive,
that's your problem. Lots of apps have problems with case sensitive drives so you should never use case sensitive file system unless you have a compelling reason to do so. Your only recourse now is to move your data to a non case sensitive drive. Clone your hard drive to an external drive, boot from the leopard install DVD, reformat the drive non case sensitive and install leopard on it. then use migration assistant to migrate your data from the external.

CS4 and Case Sensitive File Systems

Does anyone know if CS4 will support case sensitive file systems?

While I do wish all software companies including Apple completely
supported the case-sensitive file system. Many don't. I cannot pull up
an article, but I remember reading that Apple only recommended the use
of the case-sensitive file system for OS X server and if memory serves
even for that it only recommended it for the attached hard drives.
We can lament the lack of support but if you really want to change the
status quo for Adobe products then the only useful way to do so is:
...Mike

What is HFS case sensitive file system

What is HFS case sensitive file system?

FlowerChick,
a HFS case-sensitive filesystem would allow you to have files that differ only by case in the same folder; for example, you could have different files named “FlowerChick” and “flowerchick” in the same folder. On a case-insensitive filesystem, that wouldn’t be allowed.

Print dialog options in case sensitive file system

Since changing the file system running Lion and Mountain Lion from Mac OS Extended (Journaled) to Mac OS Extended (Case-sensitive, Journaled), certain features in print dialogs have disappeared.
Particularly the option to print notes with slides in Microsoft Powerpoint are gone. Also, when choosing to print only 1 (or more, but not all) of multiple pages in Microsoft Word, the printer will nevertheless print all pages.
This problem occurs on printers of different brands, i.e. HP, Lexmark, Brother.
I was able to determine this problem by reproducing the issue on a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Case-sensitive, Journaled) vs a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Journaled), not Case-sensitive.
Has anyone else had the same problem and maybe a solution?

I just fixed this on my Mac. It is a bug in Microsoft Office... the Printer Dialog Extension (PDE) for Powerpoint is located in a directory named "Plugins", but PowerPoint is looking for it in "PlugIns". This obviously does not work in a case-sensitive filesystem.
Here are the steps to fix the issue:
http://apple.stackexchange.com/a/119974/69562

HFS and case sensitive file systems

I recently received a pre-installed Macbook. The file system is HFS+ (Apple_HFS according to 'diskutil list').
This file system is not case sensitive but I would like it to be. Is there a way to deactivate the HFS wrapper responsible for that without formatting the disk and re-installing the OS from scratch ?

I got issues synchronizing my linux account with my macosx account
If it's home directory contents that's the issue, you might consider simply partitioning your drive and creating a separate home directory partition that is case sensitive, separate from the boot partition tht is not.
Assuming you're on an Intel-based machine, you can resize the existing partition to make room, then create a new case-sensitive partition and move your home directory there.
Now your account synchronization shouldn't have an issue and you didn't have to re-install the entire OS.

CS5 install on case-sensitive file system - can't choose different drive (Mac OS)

I just upgraded my macbook pro to a new drive and 10.6, and chose 'case sensitive' HFSX, 'cause I'm a heavy command line user and wanted the maximum BASH experience.
I'm trying to install the CS5 demo to try some web design tools, and the installer immediately says "Installation to case-sensitive drives is not supported. Please choose a different drive location to install." So case-sensitive drives aren't supported; crappy but fair enough.
The error message leads me to think that I can just choose a non-case-sensitive drive to install to, but I never get a chance to pick one - I click on the installer and it goes straight to the error message.
So - how do I pick a different drive to install to? Am I just an idoit, is there no way to select a different drive, or will it not install on a system that even BOOTS from a c.s. drive, regardless of the format of the drive that CS5 is installed to?
I called the support number, and the poor fellow on the other end suggested I re-download the demo, and if the new download fails call Apple support to report my 'drive error'.
I'm hoping to avoid an entire backup-reformat-restore and lose CLI compatibility just to try some demo software.
ch

That is part of why I would prefer case sensitive by default.   I know some server packages do the folding for you, same as some web servers do not differentiate between 'htm' and 'html' when people type in requests, but most of the time the backend server is going to be case sensitive and it is not safe to assume (or hope) that the service will fix things. Compensating for mistakes is fine, but allowing such silent corruption is not a terribly laudable things and it encourage people be careless.
Every once in a while I do encounter someone submitting some work where their configuration values and file names do not match, and 'well my laptop silently fixes it for me since it does not care' is a poor excuse. And if I sent broken filenames upstream or even worse commit them to be used on a server, that is a pretty significant professional failure.
Back to Adobe specifically, I have been trying the suggestion on poster mentioned in where one installs the Adobe applications to a case insensitive drive then copy over the installed files. This does not quite work out of the box, but for reasons I would be hard pressed to believe are Apple's fault.
For instance the first error I encounter is the inability of Bridge to load:
"@executable_path/../Frameworks/WRServices.framework/Versions/A/WRServices"
When I go look inside the app directories I can see that in Bridge the file has been named 'awrservices', but in Illustrator it is correctly named AWRServices.   So it looks more like a problem in whatever version control they are using. The only way I can picture (which my adminitialy limited knowledge of what I am sure is a large and complex project with all sorts of legacy issues) that the installer toolchain factors in as a problem is if they have mismatches in their own scripts/packaging and have been depending on HFS's bad behavior to hide the problem. I can understand not wanting to invest the time to pay down the technical debt on such an issue, but having such errors in your configuration causes long term headaches.
And I say this as someone who worked on just such a project, moving a software suite that had legacy code stretching back longer than Adobe has existed as a company. This conversion included moving from a case insenstive filesystem to a case sensitive one and yeah, there were lots of problems that the old FAT32 system hid from us, but it really paid off over the long run to fix them rather than try to twist the code to compensate.
Having said that, if the problem is really that they do not want to go update their filenames (in version control or config files), then you can always add folding to your loaders. I have had to do that a few times due to upstream people developing on case insensitive systems and sending data files with incorrect file names. This is an old class of problem, and while I can empathize with the struggles project managers have trying to get approval for paying down technical debt, the problem never gets better on its own and usually gets worse.
Which is why I responded with so much grump to the 'I never needed it' argument since that is exactly the type of customer comment that marketing tends to point to in order to push such things off the schedule. This is the type of thing where the customer does not really know what they want because they are already accustomed to broken behavior and most of the problems are hidden from their immediate view. It is easy to cover up the limitations since modern UI (and their search capabilities) can handle this.
It is not just arcane developers stuff, and it is the same transition that people have made with things like spaces, quotes, and parentheses, where years ago users believed they had no need for them since they were not using them, but they were only not using them because they did not work.   Today try to tell a modern user they can not put (, ", ) or even ' ' in their filenames and they would rightly question why this piece of obvious functionality is not working since today they are used to it working and no longer automatically compensate for it.
I also find it ironic that by default OSX hides a number of file extensions, so from the user's perspective you can have multiple files with the exact same name displayed to them, so you can get display issues where 'foo' is the same as 'foO' if both have .txt, but 'foo' and 'foO' are not the same if one has .txt while the other is .pdf. Add to this confusion cases like 'foo.txt' and 'foo.pdf" both being shortened to 'foo'.

HFS File system with case sensitive is not accepted to install creative cloud? Is there any other way but install the whole MacOS again after formatting the drive. I cannot belief that Adobe is so bad to it's Mac customers..

After many hours setting up OS10.10 from he scratch the last step should be installing m Adobe apps again.
trying this I always get the error message that creative cloud does not accept case sensitive file systems and I shall use another drive.
This means I have to set up the whole machine again after formatting without case sensitive but then having copy problems with my NAS?
I cannot belief that Adobe is really demanding this. If so this would show how urgent this market need alternatives and some more competition...

Hi,
You can refer below link for more information.
Error "Case-sensitive drives not supported" or similar install error | Mac OS

FileVault Doesn't Work With Case-Sensitive Journaling?

Hello,
I'm not finding anything on this topic via searches. Bought Leopard, erased the hard drive, installed Leopard with Case-Sensitive Journaling, and now Leopard won't enable FileVault. This is being done on a MBP bought in August 2007; another MBP running Leopard with regular Journaling, and bought in early 2006, has allowed FileVault to be enabled. Both MBPs have installed the available updates.
SysPrefs claims FileVault requires Mac OS Extended, and Disk Utilities clearly shows that the volume is formatted appropriately, but it's not recognizing this as being the case.
See linked screenshots.
http://www.emoore.org/etc/FileVault.Error.1.png
http://www.emoore.org/etc/FileVault.Error.2.png

In general it is not recommended to use the case-sensitive file system. Not all 3rd party apps can deal with it, especially if you have two files with the same name but different cases.

Installation of Flash Player 11.9 under OSX fails with case-sensitive filesystem!?

The installation of flash player 11.9 aborts with an unspecified error. I running OSX 10.9 with an case-sensitive filesystem. Can anyone confirm there are problems with the installer on case-sensitive filesystems?

The problem isn't the filesystem per se. It's bad software quality if pathnames defined wrong or multiple times with different notation. Often there is only one or two letters with the wrong upper or lower case. I guess in the current Flash installer this is the case. With the previous versions I had no problems.
Am 03.11.2013 um 00:41 schrieb Mike M <[email protected]>:
Re: Installation of Flash Player 11.9 under OSX fails with case-sensitive filesystem!?
created by Mike M in Installing Flash Player - View the full discussion
My Mini isn't case sensitive, so I can't really say but I had two iMacs when I worked at Intuit that were case sensitive and they had all kinds of software installation issues. One of the Mac developers at Mountain View told me that Case Sesnitive shouldn't be chosen as a format except when a system is isolated and used as a testing server. For a workstation or home computer, it's a terrible choice for a setup.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5809947#5809947
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5809947#5809947
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5809947#5809947. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Installing Flash Player at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Using an External Drive with a ReiserFS File System

I hope this is the most appropriate place to ask this question.
I am looking at adding a SimpleShare NAS device (Made by SimpleTech) to my home network. I am told that the hard drive uses the ReiserFS file system (which is a Linux file system). Two questions?
Does anyone have any experience with the ReiserFS file system? Does it play well with OS X?
Anyone familiar with the SimpleShare units? Any feedback good or bad?
Thanks for any suggestions.
David

After doing some research I determined that ReiserFS is a journaled Linux file system and having started to use it, it is working well on the network.

BUG - FTP with case sensitive server

My provider uses case sensitive file and directory names. I
created a directory 'OtherStuff' on the server directly (not from
remote view). In Dreamweaver's FTP setup I erred by specifying the
subdirectory of 'otherstuff'. When I created a default html file
and PUT it, FTP failed to find the directory but continued and put
the default html file in the root, overwriting my default web file.
Yes, I erred. However, it would be good if Dreamweaver would
stop when it encounters a cd failure.

jjstafford wrote:
> My provider uses case sensitive file and directory
names. I created a
> directory 'OtherStuff' on the server directly (not from
remote view). In
> Dreamweaver's FTP setup I erred by specifying the
subdirectory of 'otherstuff'.
> When I created a default html file and PUT it, FTP
failed to find the
> directory but continued and put the default html file in
the root, overwriting
> my default web file.
>
> Yes, I erred. However, it would be good if Dreamweaver
would stop when it
> encounters a cd failure.
>
>
You can enable case sensitive link checking in the site
manager.
However, this is more the issue of the OS, rather then DW.
Windows -
which is the OS you use, I assume - is about the only OS
(that I know
of) which is case insensitive!
All Linux/Unix based servers are case sensitive.

Firefox CTRL+F Search bar searching with Case Sensitive

is this only for me or all ?
Fiefox search bar is working with case sensitive.. if i type in capital.. it is only showing the results with capital.
for example. Type "vishnu" in search bar. it will only show you the small vishnu below.
VISHNU vishnu
is it a bug ? or is it a feature ? if it is a feature, i want to disable it :(

You can remove the check-mark on Match Case if you open the Find bar via Ctrl+F (Edit > Find).

How can I deal with case-sensitive filenames referred to inconsistently inside other files?

I have downloaded into Dreamweaver an existing web site that I'll be taking over from someone else. The site was built with Microsoft Front Page and apparently now runs on a Windows web server. While redesigning the site, I'd like to upload it to a web server belonging to me, where I can maintain a work in progress that is accessible to others (so they can give me input as I go along). But my site is running on a Unix system, where filenames are case-sensitive.
In the site I've inherited, I've discovered at least one file that is referred to in other files sometimes with one character in upper case and other places in all lower-case. The actual filename contains the upper case character and locally, on my Windows system, it doesn't matter. But on the server the file is not found when it is referenced in all lower-case.
Of course, I can create an all lower-case symlink on my Unix server for the mixed-case file that I know about. But I don't want to look through every file on the site for other files which may vary, case-wise, in how they are referenced. Is there any way that Dreamweaver can help me; for example, by going through and changing all mixed-case filename references inside files, to be consistent with the actual filenames?
I know this is a lot to ask of Dreamweaver and I'm not optimistic. But if anyone knows of a solution, I'd appreciate it.

he means that if you use the file > find function
(on windows this can be called upoon using CTRL + F)
you will be able to go through all the files which are cauing you a problem and change their names so that they are all in the same case
be warned thou
if case sensitivity is your problem,
and
if some code references to your files are written in one case and some are written in the other case, simply changeing the case of the file names will not help.
what you are trying to do will only work if
> ALL of the file names are in one case
or
> ALL of the files names are the same case
bcause this will mean you can change the one which does not always match using CTRL + F
if there is a mix and match on both sides then you are in for a lot of work, if this problem involves multiple names then i would advise you to simply start over!

ColdFusion Builder with case sensitive file system on Mac?

Similar Messages

Maybe you are looking for