Case-Sensitive rename in Windows shells

I tried to rename folder with same name:
PS C:\Program Files> ren .\nodeJs nodejs
ren : Source and destination path must be different.
At line:1 char:1
+ ren .\nodeJs nodejs
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : WriteError: (C:\Program Files\nodeJs:String) [Rename-Item], IOException
+ FullyQualifiedErrorId : RenameItemIOError,Microsoft.PowerShell.Commands.RenameItemCommand
PS C:\Program Files>
I did little digging and found there is an eight years old ticket on Connect:
https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=171545&SiteID=99
While the workaround is straightforward (to rename to temp and swap names), wouldn't it make sense to introduce a switch "-c" or "-CaseInsensitive"? Do you guys have this on your backlog?
- a citizen of Microsoft Developer Network.

@David Wyatt, I thought we would need MoveFileEx file management API (C++) function in .NET:
[DllImport("kernel32.dll", SetLastError=true, CharSet = CharSet.Auto)]
static extern bool MoveFileEx(
[In] string lpExistingFileName,
[In] string lpNewFileName,
[In] MoveFileFlags dwFlags
const int MoveFileRelaceExistingFlag = 1;
bool Rename(string oldName, string newName)
return MoveFileEx(oldName, newName, MoveFileReplaceExistingFlag));
To PowerShell (and other shell) teams:
Please add a switch to Rename-Item (aka ren) command, and close the aforementioned years old bug report on Microsoft Connect (posted in 2006 and we are still optimistic :o).
Also, if its possible in the next version of Windows/WMI~PowerShell, add the
true maximizing
(corner to corner) ability in Windows shells like Ubuntu, Mac and other flavors of *nix. For what ever historical reason this behavior is not changing, it makes it less user-friendly for some people, working intensively in shell environments;
Git, Visual Studio's command prompt, PowerShell, Ruby irb, NodeJS and since so forth.
Thank you.
- a citizen of Microsoft Developer Network.

Similar Messages

Case Sensitive Check

Hi,
Is there any way, java could differentiate case sensitive file names or folder names on a windows machine, i think its possible on a linux box. can anyone help me on this
thanx

Java on windows and Java on Linux are the same. The operating systems on the other hand are not: windows is case insensitive and Linux is case sensitive. So there is no need to differentiate case sensitive filenames on windows as you cannot have two files with the same name in the same folder.

Renaming filenames and case-sensitivity: a race condition in the OS?

There appears to be a curious set of circumstances where the OS doesn't allow you to rename a file where the only changes are case-sensitive. For example, "foo.JPG" to "foo.jpg". You can see an example using the command-shell "tcsh". Start this shell (type "tcsh" at any command prompt), and then type:
% touch foo.JPG
% mv foo.JPG foo.jpg
overwrite foo.jpg? (y/n [n])
Now, you may think it's no problem because few people use tcsh, but the problem is more systemic that should be addressed because I'm finding the problem at a programming level as well. The simplistic tcsh example illustrates the problem: the internals of tcsh call the OS-layer library function rename(2) to move or rename a file. However, something in the OS that reports back that the new filename exists (even though it doesn't) Because it sees foo.JPG, and it doesn't differentiate letter case, it thinks foo.jpg exists, so it returns an error to the calling program. In this case, it's tcsh, which is what prompts the user to overwrite. It doesn't matter what you answer, the result is the same. If you say yesthe OS doesn't see them as different, so it doesn't do anything.
If you're a programmer, you can see this happen for yourself by writing a small program that does the same thing:
#!/usr/bin/perl
if (!rename "foo.JPG", "foo.jpg") {
print "Error: $!\n";
This simple perl script just calls the rename(2) library call, which is part of the OS.
What I don't understand is why this error happens, when, and how to get around it. Obviously, other programs that rename files don't have this problem. The default shell, bash, doesn't have a problem either--even though tcsh (also a similar command-line shell) does. In fact, most programs don't have this problem. But as a programmer, I'm not sure what I should be doing. This exact same perl script (and correlating C programs) work perfectly well on all other unix platforms I've tried.
G5 Mac OS X (10.4.5)

It's not at the os layer, it's at the filesystem
layer. The filesystem you have is not case sensitive.
well, the filesystem is part of the operating system, although it's clearly only one component of it. In fact, one of the primary defining characteristics of unix is how the filesystem works, albeit there are variations of implementation. But this is a nit=picking point.
As to the issue of whether the filesystem truly is case-insensitive, that isn't so clear. I can rename a file from foo.JPG to foo.jpg easily in the Finder (just click and edit a file to change it's name from upper to lower, or mixed), and the new name you give it DOES change. similarly, I can do this with virtually any other app that has a file-finder style dialog box. Why I can't do it with the shell (or at an API level) is the real mystery, and there is no doc on the subject that I'm aware of. Clearly, the OS is preserving the change somewhere, somehow. the question is, who's doing it? (and if it's not part of the filesystem, why?)
It could be that some other layer is sitting on top of the filesystem that is overseeing such actions, and is preserving the case of the filenames, but this is such a huge waste of time and work, all for a "feature" whose value is still as yet unclear to me.
If it is, as you say, that "my version" of the filesystem happens to be case-insensitive, I'd love to know where that came from, and what the rationale was behind it. And, of course, how to get some version of the filesystem that doesn't have this feature. I've been working with unix systems at every layer since 1983, and have never run into such a thing before.
dan

How to Configuring case sensitivity for NFS on Windows Server 2012

Configure Case Sensitivity for File and Folder Names
http://technet.microsoft.com/en-us/library/cc725747.aspx
To configure case sensitivity for file and folder names using the command prompt
Open a command prompt.
To enable case sensitivity, type:
nfsadmin server [ComputerName] config casesensitivelookups=yes
But, "casesensitivelookups" is removed in Windows 2012 version.
Help Me~

Hi,
Sorry for the delayed response.
According to the following article, we still can use
nfsadmin to configure case sensitivity for Server for NFS in Windows Server 2012.
Nfsadmin
http://technet.microsoft.com/en-us/library/cc771599.aspx
Note:We
need to disable Windows kernel case-insensitivity in order for Server for NFS to support case-sensitive file names. We can disable Windows kernel case-insensitivity by clearing the following registry key to 0:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel
DWORD “obcaseinsensitive”
Hope it helps.
Best regards,
Frank Shen

HT1553 My motherboard failed and was replaced at the Apple store but I did not have my backup with me for the tech to download. When I try to download, a window comes up that the volume has the wrong case sensitivity and will not download. Thank you for a

I did not have my backup with me when my hard drive failed and was replaced at the Apple store. Now it will not download to my new hard drive. A message says that "the volume has the worng case sensitivity for a backup". How can I resore my data from the backup?
Thank you

This is a user-supported board. You are not addressing Apple here. Nor is it a good idea to post your private information to a public forum. You should edit your post immediately.
Unfortunately no one here can access your support history. You must respond to the emails directly.

How can I backup data from a case-sensitive volume to a NON-case-sensitive volume?

The case-sensitive volume in this instance being a desktop-mounted disk image volume.
A tragi-comedy in too many acts and hours
Dramatis Personae:
Macintosh HD: 27" iMac 3.06GHz Intel Core 2 Duo (iMac10,1), 12 GB RAM, 1 TB SATA internal drive
TB1: 1 TB USB external drive
TB2: 2 TB USB to Serial-ATA bridge external drive
Terabyte: a .dmg disk image and resulting desktop volume of the same name (sorry, I don't know the technical term for a .dmg that's been opened, de-compressed and mounted -- evanescently -- on the desktop)
Drive Genius 3 v3.1 (3100.39.63)/64-bit
Apple Disk Utility Version 11.5.2 (298.4)
Sunday morning (05/08/11), disk utility Drive Genius 3's drive monitoring system, Drive Pulse, reported a single bad block on an external USB2.0 1TB drive, telling me all data would be lost and my head would explode if I didn't fix this immediately. So I figured I'd offload the roughly 300 GB of data from TB1 to TB2 (which was nearly empty), with the intention of reinitializing TB 1 to remap the bad block and then move all its data BACK from TB 2. When I opened TB1's window in the Finder and tried to do a straight "Select All" and drag all items from TB1 to TB2, I got this error message:
"The volume has the wrong case sensitivity for a backup."
The error message didn't tell me WHICH volume had "the wrong case sensitivity for a backup," and believe me, or believe me not, this was the first time I'd ever heard that there WAS such a thing as "case sensitivity" for a drive. I tried dragging and dropping some individual folders -- some of them quite large, in the 40GB range -- from TB1 to TB2 without any problem whatsoever, but the majority of the items were the usual few-hundred-MB stuff that seems to proliferate on drives like empty Dunkin' Donuts coffee cups on the floor of my car, and I didn't relish the idea of spending an afternoon dragging and dropping dribs and drabs of 300GB worth of stuff from one drive to another.
Being essentially a simple-minded soul, I had what I thought was the bright idea that I could get around the problem by making a .dmg disk image file of the whole drive, stashing it on TB2, repairing and re-initializing TB1, and then decompressing the disk image I'd made of TB1, and doing the "drag and drop" of all the files in resulting desktop volume to TB1. So I made the .dmg of TB1, called "Terabyte," stashed that .dmg on TB2 (no error messages this time), re-initialized and then rebooted the iMac from my original Snow Leopard 10.6.1 disks and used Disk Utility to erase and initialize TB1 -- making sure that it was NOT initialized as case-sensitive, and installed a minimal system on TB1 from the same boot. Then I updated that 10.6.1 system to 10.6.7 with System Update, and checked to see that Disk Utility reported all THREE drives -- internal, 1TB, and 2TB -- as Mac OS Extended (Journaled), and no "case sensitive" BS. I also used Drive Genius 3's "information" function for more detailed info on all three drives. Except for the usual differing mount points, connection methods, and S.M.A.R.T. status (only the Macintosh HD internal, SATA 1TB drive supports S.M.A.R.T.), everything seemed to be oojah-***-spiff, all three drives showing the same Partition Map Types: GPT (GUID Partition Table.) Smooth sailing from here on out, I thought.
Bzzzzt! Wrong!
When I opened the Terabyte .dmg and its desktop volume mounted, I tried the old lazy man's "Select All" and drag all items from the desktop-mounted drive "Terabyte" to TB1, I got the error message:
"The volume has the wrong case sensitivity for a backup."
I then spent the next three hours on the phone with AppleCare (kids -- when you buy a Mac ANYTHING, cough up the money for AppleCare. Period.), finally reaching a very pleasant senior tech something-or-other in beautiful, rainy Portland, OR. Together we went through everything I had done, tried a few suggestions she offerred, and, at the end of three hours, BOTH of us were stumped. At least I didn't feel quite as abysmally stupid as I did at the beginning of the process, but that was all the joy I had gotten after two solid days of gnawing at this problem -- and I mean SOLID; I'm retired, and spend probably 12 hours a day, EVERY day, at the keyboard, working on various projects.
The AppleCare senior tech lady and I parted with mutual expressions of esteem, and I sat here, slowly grinding my teeth.
Then I tried something I don't know why I was so obtuse as to not have thought of before: I opened Apple's Disk Utility and checked the desktop-mounted volume Terabyte (Mount Point: /Volumes/Terabyte), the resulting volume from opening and uncompressing the .dmg "Terabyte".
Disk Utility reported: "Format : Mac OS Extended (Case-sensitive)." Doh!
Obviously, TB1, the 1 TB USB external drive I'd actually bought as part of a bundle from MacMall when I bought my 27" iMac, and which I had initialized the first day I had the iMac up and running (late November 2009), had somehow gotten initialized as a Case-sensitive drive. How, I don't know, but I suspect the jerk behind the keyboard. Whatever the case, when I created the Terabyte disk image (the drive's original name: when I erased and re-initialized it -- see above -- I renamed it "1TB" for quick identification), the original drive's "Case-sensitive" format was encoded too. So when I tried to drag and drop EVERYTHING from the desktop-mounted volume "Terabyte" to the newly initialized and "blessed" (now THERE's a term from the past!), the system recognized it as an attempt as a total volume backup, and hit me with "The volume [the desktop-mounted volume "Terabyte" -- BB] has the wrong case sensitivity for a backup." And, of course, the reinitialized TB1 was now correctly formatted as NOT "case-sensitive."
Well, that solved the mystery (BTW, Disk Utility identified the unopened Terabyte.dmg as an "Apple UDIF read-only compressed {zlib}, which is why the .dmg file could be copied to ANY volume, case sensitive or not), but it didn't help me with my problem of having to manually move all that data from the desktop-mounted volume "Terabyte" to TB1. I tried to find a way to correct the problem at the .dmg AND opened-volume-from-.dmg level with every disk utility I had, to no avail.
Sorry for the long exposition, but others may trip over this "case-sensitive" rock in the road, and I wanted to make the case as clear as possible.
So my problem remains: other than coal shovel by coal shovel, is there any way to get all the data off this case-sensitive desktop-mounted volume "Terabyte" and onto TB1.
Not that I know whether it would made any difference or not, one of the things that got me into this situation was my inability to get "Time Machine" properly configured so it wasn't making new back-ups every (no lie) 15 minutes.
Philosophical bonus question: what's the need for this "case-sensitive," "NOT case-sensitive" option for disk initialization?
As always, thanks for any help.
Bart Brown

"Am I to understand that you have a case-sensitive volume with data that you want to copy to a case-insensitive volume? And the Finder won't let you do it? If that's what the problem is, the reason should be obvious: on the source volume, you may have two files in the same folder whose names differ only in case. When copying that folder to the target volume, it's not clear what the Finder should do."
Yes, I understand all that... NOW.
What I had (have) is a USB external 1TB drive (henceforth known as "Terabyte") that I bought with my 27" iMac. I formatted, and put a minimal (to make it bootable) system on Terabyte the same day back in late November 2009 that I set up my 27" iMac. Somehow -- I don't know how -- Terabyte got initialized as "case-sensitive." I didn't even know at the time that there WAS such a thing as "case-sensitive" or "NOT case-sensitive" format.
Sunday morning (05/08/11), Drive Pulse, a toolbar-resident utility (that's Part of Drive Genius 3) that monitors internal and external drives for physical, problems, volume consistency problems, and volume fragmentation, reported a single bad block on the volume Terabyte, advising me that it would be best if I re-formatted Terabyte ASAP. I thought I could open Terabyte in a Finder window, Select All, and drag everything on the drive to ANOTHER USB external drive of 2 TB capacity (henceforth known as TB2). When I tried to do that, I got an error message:
"The volume has the wrong case sensitivity for a backup."
First I'd heard of "case sensitivity" -- I'm not too bright, as you seem to have realized.
Oddly enough (to me), I could move huge chunks of data, including a folder of 40GB, from Terabyte to TB2 with no problem.
Then the scenario unfolded per my too-convoluted message: several hours of trying things on my own, including making a .dmg of Terabyte (henceforth to be known as Terabyte.dmg) -- which left me with the exact same problem as described in the previous 4 paragraphs; and my 3 hours on the phone with AppleCare, who at least explained this case-sensitive business, but, after some shot-in-the-dark brainstorming -- tough to do with only one brain, and THAT on the OTHER end of the line -- the very pleasant AppleCare rep and I ended up equally perplexed and clueless as to how to get around the fact that a .dmg of a case-sensitive volume, while not case-sensitive in its "image" form (Terabyte.dmg), and thus able be transferred to TB1 or TB2 with no problems whatsoever, when opened -- either by double-clicking or opening in Disk Utility -- produced a desktop-mounted volume (henceforth known as the volume "Terabyte," the original name of the case-sensitive volume from which TB1.dmg had been made) that had the same case-sensitivity as the original from which it was made.
In the meantime, having gotten the data I needed to save off the physical USB "case-sensitive" volume Terabyte in the form of Terabyte.dmg, I erased and re-initialized the physical USB "case-sensitive" volume Terabyte, getting rif of the case sensitivity, and renaming it TB1. But it all left me back at square one, EXCEPT I had saved my data from the original "Terabyte" drive, and reformatted that drive to a NON- case-sensitive data now named TB1. The confusion here stems from the fact that problem case-sensitive drive, from which I made Terabyte.dmg, was originally named "Terabyte". When I re-initialized it as a NON case-sensitive drive, I renamed it TB1. I'm sorry about the confusing nomenclature, which I've tried to improve upon from my original message -- usual text-communication problem: the writer knows what he has in mind, but the reader can only go by what's written.
So, anyway, I still have the same problem, the desktop-mounted volume "Terabyte" still cannot be transferred in one whole chunk to either my internal drive, TB1, TB2, as the Finder interprets it as a volume backup (which it is), and reads the desktop-mounted volume "Terabyte" as case-sensitive, as the original volume -- from which the disk image Terabyte.dmg was made -- had been at the time I made it.
"As long as that situation doesn't arise, you should be able to make the copy with a tool that's less fastidious than the Finder, such as cp or rsync."
I'm afraid I have no idea what "cp or rsync" are. I'd be happy to be educated. That's why I came here.
Bart Brown
Message was edited by: Bartbrn
Just trying to unmuddy the water a bit,,,

How can I transfer my iphoto library from a Mac OS Extended (Case-sensitive, Journaled) harddrive to a Mac OS Extended (Journaled) hard drive?

Community,
Every time I try to transfer my iphoto library from a Mac OS Extended (Case-sensitive, Journaled) harddrive to a Mac OS Extended (Journaled) hard drive, I receive the attached message: "You can't copy 'iPhoto Library' because it has the same name as another ideon on the destination volume, and that volume doesn't destinguish between upper- and lowercase letters in filenames."
My theory is, if I am able to unpackage my iphoto library, I can transfer each folder one at a time so that I can trouble shoot any "duplicates." Will this work?
Let's say that works. How can I repackage the library so iphoto recognizes it?
Is there a better way?
Thank you,
Jonathan

Can we assume that I don't have any naming conflicts? Clearly there are or else I wouldn't get the error I'm getting.
The error doesn't mean you have name conflicts. It means that the Finder won't take the chance that you might have them.
You're suggesting that all I would need to do would be to use Carbon Copy Cloner to transfer the files from the case-sensative harddrive to my Extended Journaled harddrive?
Yes. But I would just use the built-in rsync shell command. First, back up all data if you haven't already done so. Launch the Terminal application by entering the first few letters of its name into a Spotlight search. Copy or drag -- do not type -- the line below into the Terminal window, then press the space bar:
rsync -aE --delete
Now drag the iPhoto library you want to copy into the window. You should have something like this:
rsync -aE --delete /Users/you/Pictures/iPhoto\ Library
Drag the Pictures folder on the destination volume into the window. Now you have this (line will wrap on the page):
rsync -aE --delete /Users/you/Pictures/iPhoto\ Library /Volumes/something/Users/you/Pictures
Press return. The copying operation will start. When it finishes, you'll see a new dollar-sign ("$") prompt below what you entered. If there were no errors, you're done.

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!

How do I convert a case sensitive drive to a case insensitive drive?

I have recently purchased a MacMini Server, and installed the 2 internal hard drives in a RAID 0 configuration to obtain the speed and 1 TB capacity, but unfortunately (rather stupidly in retrospect) formatted the drive in case sensitive mode.
On installing the operating system and multiple applications, everything seemed to work well until I tried to install Adobe Acrobat X Pro. This application refuses to install on a case sensitive formatted drive, which I now understand is a common problem.
The question is how can I convert to a case insensitive format without reinstalling all of the software from scratch?
I have a Time Machine backup, and the easiest thing for me would be to reformat the drive, and then restore from the Time Machine backup.
Will this process work? Or will there be some complications and files that will not function if they were originally installed on a case sensitive drive?
Any help is appreciated....

iPartition can do it ( http://www.coriolis-systems.com/iPartition.php ).
from iPartition Help:
Make Case Sensitive/Case Insensitive
HFS+ now supports a case sensitive format as well as the usual case insensitive format. On a case sensitive volume, the names “Readme”, “README” and “ReadMe” would all represent different files, even if they were in the same folder.
This option allows you to non-destructively change a case sensitive volume into a case insensitive one, and vice-versa. If you are going from a case sensitive volume to a case insensitive volume, some of your files may be renamed automatically by iPartition so that they do not clash. If all of the files in the table below were in the same directory, the right hand column shows the new names iPartition would choose for them:
Old name New name
README.txt README.txt
ReadMe.txt ReadMe 1.txt
Readme.txt Readme 2.txt
README README
ReadMe ReadMe 1
Readme Readme 2
Notice that iPartition puts the number before any file extension.
N.B. iPartition does not transform filenames with numbers on the end back into their original forms. There is no way to tell which files were renamed by the user and which were renamed by the conversion process.

How can I copy media from an HFS case-sensitive drive to an HFS case-insensitive drive without getting an error?

About a year ago, I accidentally created a partition on my drive for my iTunes Music. On that parition, called MUSIC, I selected the filesystem to be an HFS, Journaled, case-sensitive partition. Since then, all of my music, new and old, lives on the case-sensitive MUSIC parition.
My other partition, called BOX, is an HFS, Journaled, case-insensitive filesystem, as are my external drives I use for archiving and backing up my music.
My dilemma: when I try to copy my music/iTunes media from the MUSIC partition to a different partition that's case-insensitive, I obviously run into errors saying that certain files can't be copied because they will overwrite others. Subsequently, I can't back up my music and iTunes media to another drive unless it has the same filesystem parameters favoring case-sensitivity. I want to move my media to a case-insenstive drive/partition.
As the story goes, I'd like to avoid having to reformat and worry about moving my media around because I feel, in the end, I'd end up doing more harm then good in my pursuit to fix this issue.
My question: is there some way I can detect which files are conflicting with each other, and then manually rename them? My music library runs about 16,000 songs deep, but I'd still feel saved even if I had to go through and manually rename all of the music files so they don't conflict with each other in order to get them on to a case-insensitive drive. Perhaps there's an AppleScript someone knows about that I could execute in my MUSIC partition to see which files/directories are causing my problems? In other words, I'm thinking there could be a way to detect the same file/directory names that are only different soley because of their case.
Any help, suggestions, or solutions are welcome. Thank you all for your time in helping me solve this!
And have a Happy Thanksgiving

How do I restore a case-sensitive,...: Apple Support Communities

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

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.

Copying folders & files from case-sensitive to non-case-sensitive volume

I'm trying to copy a rather large (60+ GB), folder and all its enclosed items from a volume that is has case sensitive file names to one that does not. The copy operation always stops when it comes across a duplicate file/folder name differing only in the case of some of the characters. The folders/files in question are actually not duplicates, so I would like to change the file name of the duplicate by appending anything to the filename.
The copy operation does not provide any choice but to abort the operation when it finds the first identical file or folder name differing only in case..
Any suggestions?

Unfortunately, that is not a viable solution, as I am tring to convert a case sensitive volume to a non-case sensitive volume.
What I would like is a method to copy files and when a duplicate occurs it asks me what to do like rename the second duplicate. However this problem is now moot, as I painstakingly renamed each offending file/folder as each error occured, and then restarted the copy.
While the question is not answered, I am marking it as such because I am now past the problem.
Thanks for your response.

File System Case Sensitive - breaks Write-Once

I don't find a System property that denotes if the file system is case sensitive.
If I want a FileFilter to behave as the user is expecting - it must know if the file system that it is running on is case sensitive. For example: On a DOS system the file apple.txt should be returned with the file PEACH.TXT by a FileFilter that is accepting *.TXT files. But on a Unix system only the PEACH.TXT would be returned (case sensitive).
How would I make my FileFilter a true write-once-run-anywhere class?
What am I missing?
David

For a file filter,
you can get the file name and convert it to lowercase,
then compare to a lowercase extension. It's not like
that will rename the file, the file will still have
whatever name the file has. However for a FileFilter that is case sensitive - there is a difference in what a File.listFiles(new ExtensionFilter("txt")) returns. And one can not just decide that it doesn't matter.
Here's a specfic example. On a case insensitive system what is the next file in the sequence of:
File.001, File.002, File.003, file.004
Answer: fILE.005 - is valid
But on a case sensitive system if one uses a FileFilter to find all the files that match "File".* then the answer is "File.004" - ONLY ONE answer, and creating this file will not (should not) overwrite the file.004!
Seems to me one needs to match the FileFilter to the underling OS - because chances are the user is expecting OS file system naming conventions. If the user doesn't know what file system (and can't know - like on a web server app) then the system better be smart enough to not mess up and clober files.
So it appears to me that a programmer needs to be able to ask the System what it's file system convention is. And sure I could guess based on some other properties (System.os.name or as Sun did based on file.separator) - but I was hopeful that I didn't need to GUESS.

Web Dynpro & case sensitive selection of Adobe Forms

Hi Community
how can I solve this issue:
I have a Web Dynpro View with a button. Clicking this button generates a Adobe form and displays it.
So long everything's fine.
Here's my problem:
There are 4 different case sensitive forms in dependence of the user's selection. How can I solve this?
The form is assigned to the view via layout, so do I have to create 4 views,related to the amount of forms? And additionally the pdf's are displayed in dialog windows, so do I have to create 4 windows additionally where I have to embed a view for each of them?
Is there any other way to solve it? It looks for me like a not very nice solution.
Thanks in advance,
Tan

Hi Tan,
Solutions that i am proposing may not be the best solution but you need to take a call on the best one:
Solution 1 :
1. Try Creating only one view and one window for pop up ( in addition to your existing view with button )
2. in the view add an interactive form and bind it to one of the form.
3. in WDDOMODIFYVIEW method , depending on the situation try to change the mapping to this interactive form
4. This embedded view in the pop up window is always called, only based on the conditions the adobe forms changes.
Solution 2:
1. in your view add 4 Interactive forms , bind them to different nodes as per its mapping requirement
2. create 4 Visibility context attributes , bind them with each of the forms
3. depending on the condition , hide or make visible the adobe forms.
4. show this view in the pop up window.
My suggestion would be to go with Solution 2 , since it does not involve dynamic modifications at runtime.
Regards,
Ashish Shah

Case-Sensitive rename in Windows shells

Similar Messages

Maybe you are looking for