Received Files Folder Problem

[kattnapp]

Hi Guys, I've only been using aMSN for a short while now. However there is a bug regarding the received files folder.

I have no idea where it is... Honestly. Amsn says its here "C:Program Files\aMSN\scripts\amsn_recieved\.file" However that directory doesn't exist.

I have been sent things like mp3's which I can happily play when I click open once the file has finished downloading, but to find them and move them somewhere else. Well they are in Limbo, who knows where they could be.

I've even searched my harddisk for these mythical files that I know got sent.

I am using Vista, which I know is a load of crap at the end of the day.

I have changed the directory using the preferences, other tab. But now, any files I get sent won't download.

What is going on? Help ! **waves flag!**

Cheers From Lew

[kakaroto]

Hi kattnapp, welcome to the forums!
In theory, if you go to the contact list, then click on the "Account" menu, there's an option there "Open Received files folder" which should open the folder for you... but now, since you've modified it, I guess it won't work!
Make sure that when you set the received files folder in preferences->other, that you use the Browse button to make sure the directory you enter is correct and valid so your file transfers would work again...
anyways, you should find the amsn received folder by default in :
C:\Users\kattnapp\amsn_received
or in C:\Program files\aMSN\Scripts\amsn_received
try looking there (or in C:\Program Files (x86)\aMSN\Scripts\amsn_received if you use a 64bits system)
I hope that helps!

[kattnapp]

Well, none of those directory's existed to start with even though aMSN has been downloading to C:\Program files\aMSN\Scripts\amsn_received even though it doesn't exist.

I'm at a loss what to do now, because the files are somewhere on my C:/ drive, I don't understand why they would be hidden / being in electronic Limbo.

[ElCynico]

When creating new folders, Vista automatically puts them to read-only state. Are you absolutely sure that file transfers have been 100% succesful?

aMSN also seems to be incapable of creating new folders... so, when you change the target folder, you'll have to create it manually, as well.

You have enabled 'Show hidden files and folders', have you?

[kakaroto]

Humm.. there's no C:\Users\<your windows username>\amsn_received directory? that's weird.. What path was there in the preferences->others before you changed it ?
About vista doing weird stuff, it's very possible, I've heard about it.. especially that if an application (non administrator) tries to access a read only directory like C:\Program files\, Vista puts the files somewhere else in some kind of virtual file system.. I don't know where it is though, sorry....
@ElCynico
and btw, aMSN should create directories on its own and no, it doesn't create them readonly..
also transfers were completed successfully since he could open the files with the 'Open' button of the file transfer window once it completed...

[BW]

Hi kattnapp,

my first thought was, that this is probably caused by the "virtualization feature" of Vista, as kakaroto already said.
have a look at the following folder:
"C:\Users\User_name\AppData\Local\VirtualStore\Program Files\aMSN\scripts"


more information about that can be found here:
http://support.microsoft.com/kb/927387
http://www.hanselman.com/blog/VistasShowCompatibilityFilesAndTheScrumptiousWonderThatIsFileVirtualization.aspx


@kakaroto:
usually Vista shows the button "Compatibility Files" when there are files in the corresponding VirtualStore,
the problem here is, that we have only the folder amsn_received and no files there, therefore Vista
won't show this button... so even if you know the "virtualization feature" you won't easily find your files...
so we have 3 options:
1. create a file or change any other file in "Program Files\aMSN"
2. create the folder amsn_received while installing aMSN
3. use a folder within the users profile directory for the received files, at least from Vista on

[Gordijnhoofd]

Just wanna add I had exactly the same problems with windows 7.

Thanks for the info, BW!