nickname's dashboard

wuala should encode multibyte and utf8 stutt in the urls properly. this is a standard that has been defined long ago. maybe its also the fault of the participating mailservers and mailproviders and also your mailclient problem.

if you dont provide proper information about all these components, what mailprogram you use and so on nobody can help you.

look into your uploads window once you are logged into your account. the maintenance stuff will appear there. also ctrl+alt+p (trigger check for your private files, see some other days releasenotes document). it will generate some internal check inside your wuala account and eventually triggers (faster) the maintenance elements to show up (if any). – nickname, on May 17, 2009 23:13

tis has been long ago asked for as a feature, and no it doesnt support webdav. wuala works differently. as of now there is a plain webinterface (http) to the public and part of the private (passworded) wuala content. simply start at navigating the wuala website.

http://www.wuala.com/antoine

suppose thats your nickname inside wuala, other than that, replace with your nick.

http://www.wuala.com/yourstupidnickna...

what about vista x64? does fsi work there properly? – nickname, on May 15, 2009 13:26

the wuala files on the disk are not for the enduser. maybe wuala should place a big huge (CAPS) filename in their wuala folders and point that out to the user. what kinda moron would rename the multigigabyte files of the wuala storage to whatever name he or she would think their actual file might be, and especially the sizes and all that stuff.

i wonder how lame and stupid people can get. wuala has a function or dragdrop to extract files from inside the application itself to the actual computer to make the file exist outside the wuala system.

i dont get it how people cant understand the basics of things.

dont rename or mess with stuff in your programfiles, windows or other hidden folders. on recent windows systems this is even pointed out to the user in the local file explorer windows.

maybe wuala should make its folders also hidden and system so that windows hide these contents even more.

there will always be fools who cut off their agp or pcie cards contacts to make them fit into other types of mainboard slots and so on. there is simply no end to stupidity.

speed is never a static thing on them inter-nets, its just a sample speed measurement that can be taken at every point in time.

what good is speed wizard when the internet is crowded during install or first start-up time.

id rather call for a more publicly available option to change bandwidth settings, not needing to be logged in to the client with any account. like other file-sharing clients, maybe even right-click tray-icon to set temporary or static speed limits up and down and so on. maybe even different speed limits if possible for maintenance, for initial uploading when adding files, for receiving all this meta-information, thumbnails, comments, folder listings and such things that are not actual content and the files themselves.

so we did have win7 rc1 build after all even at the end of april, and it seems that several big oems are counting on an october release. the smb components of win-wuala should rather need to get fixed real soon now.

meaning what exactly? your problem solved? close your thread then and mark it accordingly. thank you for supporting your local community. – nickname, on May 05, 2009 17:31

what do you mean legal? you are not a native english speaker i suppose. legal rights are not the point. searching for hash allows for organizing, grouping with people of similar interest, remembering or re-searching a file and being able to know where it once came from and much more. searching for all kinds of things, metainformation, tags, properties of files helps the whole community.

once upon a time there was a call for being able to construct better and more complex search queries in wuala. this feature has not yet come to pass, we are all eagerly waiting for it. please allow us to search more thoroughly and in a more sophisticated manner. maybe some acquisition or merger with google would help ):> – nickname, on April 23, 2009 15:24

even more: sometimes i wish to know where this element (even private ones) is being shared overall in other peoples wuala storage areas (public, or accessible at least).

in short: is this element already shared elsewhere? if yes, show me the other locations.

you still didnt provide any more elaborate details on the stop message of your bluescreen, the drwatson .log (text) files, or the linkback / url of the oca (online crash analysis) from microsoft if you didnt turn it off that is.

it is passwordprotected. you need to have an account before you can activate it. get over your sex and moral problem and stop watching it.

asking for yet another password or yet another control and moral authority doesnt help. your world view and problems might be quite different from others.

freedom to everybody.

not me. thats rubbish. when you bluescreen its most highly probable that its a driver related issue.

what does onlinecrashreporter say after such a bluescreen. it wants to report the blueascreen and stackdumps and whatnot to microsoft, which incase you havent disabled it can provider reliable and valuable information. ofcourse when you are paranoid and have turned off all sorts of stuff inside your os you will never see it and should actually switch to a different platform alltogether :)

anyways if there isnt even a drivername or modulename provided at the STOP error messages then its even more likely to be a hardware/driver compatibility issue or some misbehaving switches and even ethernet wirelevel bugs.

did you try to turn on/off autonegotiation on your network-cards, or on your switch, try a different switch ( i also suppose you tried both of your computers where you claim to have your bluescreen with the very same switch or even same switchport) or try such things as flow-control, speed/duplex settings and such things.

also the dhcp process is often part of the problem, try using fixed ip on your networkcard for debuggin in contrast to most likely a dhcp setup.

also: there is a microsoft registry key ever since winxp that handles this network cable detection stuff, i dont quite remember whats it called exactly, will look it up later. this stuff can mess with a lot of systems and various scenario, and microsoft provides a knowledgebase entry on howto disable it, as there were some bugs and sofware which cant handle this stuff properly.

p.s. its even there ever since win2k, so here is the knowledgebase entry:
http://support.microsoft.com/kb/239924

disable media sensing feature on windows, disable link state detection.....