Windows 7 Beta and filesystem integration?
I can't get filesystem integration to work under Windows 7 - did anybody get it to work?
If yes, could you post a step-by-step instruction how to do it?
If yes, could you post a step-by-step instruction how to do it?
23
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?No, but it is a beta; you have to wait at least for the final release
-
Inappropriate?Could be a problem with
- Windows 7
- the Java VM on Windows 7
- the FSI-library (jlan) on Windows 7
- Wualas implementation/use of the FSI library...
Since Windows 7 is still in Beta I doubt it has high priority but for the RC(s) I hope FSI will work again. What does the FSI-Log say btw.? -
Inappropriate?and additionally. If you have used the 64-bit version e.g. the 64-bit version of java the fsi will not work, cause the jlan is not 64-bit ready. ...
-
Inappropriate?Logfile from the german x86 beta:
http://www.wuala.com/posativ/Public/W... -
Hm, sounds as if either the jlan server isn't running at all or Windows doesn't want to connect... firewall or security settings or whatever.
Maybe the syntax for "net use" has changed? It would be interesting what "net use /?" and "net use \\Wua142205\La" does output on commandline in Win7 -
Inappropriate?
C:\>net use /?
Die Syntax dieses Befehls lautet:
NET USE
[Gerätename | *] [\\Computername\Freigabename[\Volume] [Kennwort | *]]
[/USER:[Domänenname\]Benutzername]
[/USER:[Domänenname im Punktformat\]Benutzername]
[/USER:[Benutzername@Domänenname im Punktformat]
[/SMARTCARD]
[/SAVECRED]
[[/DELETE] | [/PERSISTENT:{YES | NO}]]
NET USE {Gerätename | *} [Kennwort | *] /HOME
NET USE [/PERSISTENT:{YES | NO}]
C:\>net use \\Wua142205\La
Systemfehler 53 aufgetreten.
Der Netzwerkpfad wurde nicht gefunden.
C:\>
does that help in any way? -
Hm, if Wuala was running in the background that means Windows doesn't "see" the jlan-Server and this might be the issue here... interestingly it throws a different error than Wuala itself?! -
Inappropriate?Once Windows 7 reaches final state, we'll make sure Wuala runs fine with it. Please hold your horses until then ;)
regards
kaspar
The company and 1 other person say
this solves the problem
-
Inappropriate?internetexploder 8 is supposed to go rtm as early as march2009, and rcX builds of win7 are also supposed to appear still this february2009.
so guess what, win7 is gonna be pushed to the market way before the end of the year, it might appear as early as early summer time on the early adopters market, corporations and even oems might gonna get it early fall this year.
microsoft is definitely panicking as vista is the biggest mess they created so far and huge corporations and most other users would like to stay with winxp even further.
so maybe wuala should just forget about any windows beyond winxp alltogether or start win7 compatibility tests and efforts right away as it seems that win7 gold is just about to appear on the horizon.
http://www.neowin.net/news/main/09/02...
http://www.neowin.net/news/main/09/02... -
Inappropriate?I have the same problem, too... after trying
net use \\Wua206075\La (guys, you have to use YOUR private id from the fileintegration log, not the Wua142205 example written above...) on the command line, I was asked to log in with username and password. I entered both but I always get the response my password was wrong (I double checked it...) -> System-Error 86
Hope that helps...
I’m sad
-
Inappropriate?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.
-
Inappropriate?Without filesystem integration Wuala isn't very useful. One can't watch a video during download... etc. really annoying
I’m frustrated
-
Inappropriate?I hate how the Wuala team ignores this, even though Windows 7 is in Release Candidate.
I’m frustrated
-
Inappropriate?wualas filesystem integration part on windows at least is from a thirdparty java component/dll. so as long as this thirdparty doesnt come up with a solution wuala cant do shit about it. unless they go for a completely different solution, buy from a different technology provider and so on.
microsoft is constant incompatibility. sucks to be a microsoft addict :p
1 person says
this solves the problem
-
thats market date. rtm is way before. we will have rtm code by july-august if i am not mistaken. it will be on the internet all over the place. -
Inappropriate?we have win7 declared as rtm as of yesterday (which was actually long ago leaked shortly after original compile date of july 13rd 2009), so whats the stance of caleido on win7 now :)
-
Inappropriate?I am on Windows 7's final build... Please make Wuala work! You said when it reaches final state, it is, now work on it please!
I’m frustrated
-
Inappropriate?Win7 RTM (x86), waiting filesystem integration still.. Any good news from our buddies developers?
Thank you!
I’m frustrated
-
Inappropriate?RTM is out for a while; "some day, some day soon? it's going to work" no worries early Windows 7 adopters.
Please Wuala don't hurry who cares about this!
I’m amused
-
Inappropriate?http://windows7news.com/tag/windows-7...
looks like release date is 22. of Oct. Or did I miss something? -
Inappropriate?OK, I do not think that it is only about dates. Yes, it is 22nd of October. But it does not mean that the Wuala Team is going to release a new version on 23rd with filesystem integration. At least that sounds quite improbable to me.
I believe that they are working on it very hard - and not just sitting doing nothing and watching the calendar. -
Inappropriate?Yes, you missed something. Every MSDN customer and tousends of students are able to download Win 7 for free. I'm using it already and I know many more who are using it too. Vista is crap and XP outdated. So please work on this...
-
Inappropriate?RTM was released to MSDN on 6th August 2009:
http://blogs.msdn.com/msdnsubscriptio...
If you get a copy of the download, even if you don't have a license key handy you could still choose "activate later". FWIW, the SHA-1 for some official ISO downloads:
32 bit
File Name: en_windows_7_home_premium_x64_dvd_x15-65733.iso Date Posted (UTC): 8/6/2009 9:59:56 AM
SHA1: 336779EA6B65F63E11A609B4D021439C47AB315B ISO/CRC: 56D954E4
64 bit
File Name: en_windows_7_home_premium_x64_dvd_x15-65733.iso Date Posted (UTC): 8/6/2009 9:59:56 AM
SHA1: 336779EA6B65F63E11A609B4D021439C47AB315B ISO/CRC: 56D954E4
Cheers,
Shawn
I’m confused...
-
Inappropriate?My new PC also has the release build installed and still no solution with the problem. This is more than annoying - its frustrating!
Whatever the problem might be - fix it! -
Inappropriate?There are so many applications which can not run on windows 7 and for wuala it's just the FSI...
It will be fixed by the end of october.
-
Oh, which "many" do you mean? My experience is totally opposite. Even some of my apps which don't worked under vista work now unter 7 natively again. Wuala is the only application of my everyday use which does not. And the devs are the only devs of any of my everyday use applications, they didn't seem to care about it... -
Dismissing customer issues is not the way to succeed at building happy customers. I understand that you are probably waiting on JLan to ultimately fix FSI, but still not good customer support. -
@newRaven: The devs have set a date when Wuala will support Win 7 a few months ago. I think they ́ll care about it, but they have seen that they need alot of time to solve that issue. And they have announced it. Whats the problem? -
The problem are things like "The company thinks this is not a problem." or "Once Windows 7 reaches final state, we'll make sure Wuala runs fine with it. Please hold your horses until then ;)". 7 is in its final state since at least 6 weeks (MSDN-Release). And even if they care about it, they forgot absolutely to communicate with their users about it... look in this forum... look for threads which are about windows 7 problems. And now look for any "official words" with any specific content within. You'll hardly find any... THATS the damn problem. I don't blame them for not getting these stuff ready, but I DO blame them for absolutly no communication about it... no answers to questions, no progress reports... nothing at all. -
Inappropriate?btw y is it marked as "Not a problem"?
-
The bug was originally created during Win7 beta, so the Wuala team marked it "closed". Unfortunately once Windows 7 hit RTM they ignored it causing a lot of ill will. -
The bug was originally created during Win7 beta, so the Wuala team marked it "closed". Unfortunately once Windows 7 hit RTM they ignored it causing a lot of ill will. -
This was marked "not a problem" 9 month ago. I think it was ok at this time. One of the problem of GetSatisfaction is, that nobody can close a thread for writing on.. There are several thread opened for the same issue during the rtm time wich are still open. They might have been a better place to talk about this issue in the last months than this one. -
Inappropriate?Dear NewRaven,
you are absolutely correct with your critism. The communication about that problems wasn ́t good at all. We apologize for that.
We are working on a restructuring of our forum services and I think we are able to prevent such mistakes in future. Not at least there will be a bugtracker avialble soon, wich gives us a better way to inform you about the state of those problems.
Specially to this Problem: We have nearly finished our work and we will release the next update wich will include support for Win7 as soon as possible. Like promised, this should be latest with the official start of disposal of Win7.
Regards,
Bernd
2 people say
this solves the problem
-
Inappropriate?It WORKS!!!
They fixed it :-)
Did a fresh install and it works on final Win7 here.
I’m thankful
1 person says
this solves the problem
Loading Profile...





EMPLOYEE
EMPLOYEE
EMPLOYEE






EMPLOYEE