Networking (to file share) between Windows 7 and Windows XP

Mapnapkin said:

Sorry if this was answered already but if you type in \\Blackrose in your address bar does your XP machine appear?

When I type in my xp machine \\BLACK , it shows all my shared folders, also shows BLACK in the list of machines in the left column under Network.
So, what i did when I saw BLACK listed under Network is dragged it up to Favorites. Now i can easily get to it when I need.

Its not perfect but it work until windows gets it fixed.

Hope that helps
Dm

Yes i stated UNC paths work, however AquiloNow never replied if he had tried that when i asked.

Digger said:

.........right.... figured i shoulda asked WHAT build this was concerning... now i see this is about 57? Come on guys... why all the constant upgrades? find a stable build then stick with it until something proven to be a stable build has some big influencial changes in the OS.

.......

Also you will find MORE support for 7000 builds than you will for the latter builds.... unless the "community" finds a stable newer beta build (some like 48). This goes for anything, not just this OS Beta test. If you have something running great, the rule of thumb is to not try and "fix" it or "upgrade" it... or atleast be one of the firsts to do so. I learned this the hard way a long time ago with router firmware upgrades. Just a little fyi.

How does the "community" find a newer stable build if we don't try them?. In my case 7000 was very unstable 7057 is much better for me, and updates do work with 7057.

Yupyup - Sorry about that, I didn't see that originally. UNC doesn't work. :/

I created a new workgroup, named "Bracelet" and put both my XP and my W7 on it...and I can see the W7 machine on XP, but I can't access it, NOR can I even see the XP machine on W7.

YupYup said:

How does the "community" find a newer stable build if we don't try them?. In my case 7000 was very unstable 7057 is much better for me, and updates do work with 7057.

Well i like to think this is a pretty good reflection of a community. There are some wise and savvy ppl here on this forum. Search around and you tell me which build seems to be more stable after 7000.... 48 or 57? let me also remind you that 57 has been out what now, bout 2 weeks.... you shall see the results

Tho this build may work for you... tho you may also come into conflict with other things that you hadnt run into with the latter builds. Builds being thrown around like table salt... these for the most part are not meant for mainstream. Why, because for what they are "trying" may or may not be in the final release or RC1 for that matter. So while you are banging your head about a possible problem or issue on one build, it may not be included or exist in another build. Things that worked fine for others in 48 have issues in 57 upgrade or fresh. Dont take it from me, lots of folks on here are smarter than I.

Digger said:

Well i like to think this is a pretty good reflection of a community. There are some wise and savvy ppl here on this forum. Search around and you tell me which build seems to be more stable after 7000.... 48 or 57? let me also remind you that 57 has been out what now, bout 2 weeks.... you shall see the results

Tho this build may work for you... tho you may also come into conflict with other things that you hadnt run into with the latter builds. Builds being thrown around like table salt... these for the most part are not meant for mainstream. Why, because for what they are "trying" may or may not be in the final release or RC1 for that matter. So while you are banging your head about a possible problem or issue on one build, it may not be included or exist in another build. Things that worked fine for others in 48 have issues in 57 upgrade or fresh. Dont take it from me, lots of folks on here are smarter than I.

Should I be considering upgrading from 7000 build then?

AquiloNow said:

Should I be considering upgrading from 7000 build then?

I dunno.... how well do you do at the casinos?

Mine isnt broke, so no reason for me to fix right now.... i just keep reinstalling 7000 if needed. Every build will have something different or wrong or right with it, but wont be the same as the last as it looks. But for the most part, the structure of the OS is there and built, reason for the public release. Now they are at a happy stage with it and playing around with things. I just hope they dont go screwing things up as with the likes of Longhorn/Vista ... atleast for the most part, programs and games install and run well. Its the other issues of punkbuster (their own issue not MS) some steam, and some others - listed in the other subforums.

Its your call:)

Digger said:

Well i like to think this is a pretty good reflection of a community. There are some wise and savvy ppl here on this forum. Search around and you tell me which build seems to be more stable after 7000.... 48 or 57? let me also remind you that 57 has been out what now, bout 2 weeks.... you shall see the results

Tho this build may work for you... tho you may also come into conflict with other things that you hadnt run into with the latter builds. Builds being thrown around like table salt... these for the most part are not meant for mainstream. Why, because for what they are "trying" may or may not be in the final release or RC1 for that matter. So while you are banging your head about a possible problem or issue on one build, it may not be included or exist in another build. Things that worked fine for others in 48 have issues in 57 upgrade or fresh. Dont take it from me, lots of folks on here are smarter than I.

Even though it does not answer the question i will agree, and build 7048 would get my vote for best of the 3.

Ya seems like build 7000 is the most stable which is dissapointing. I like having all features included like aero peek in my main OS. Oh well

Back on topic. Seems like the only thing that doesnt work is XP access to the W7 machine to the C drive, other hard drives work fine. Also on the 7 machine you cannot see the XP machine, but typing in the IP on 7 you can share folders and files no problem. Now if only I could get network printing to work. Each time I 7 cannot find a driver and wont install it. is there anyway to find drivers separately I couldn't find any vista drivers on the canon website, they said they were part of windows update but 7 doesnt check windows update for drivers...

Somm said:

Ya seems like build 7000 is the most stable which is dissapointing. I like having all features included like aero peek in my main OS. Oh well

Back on topic. Seems like the only thing that doesnt work is XP access to the W7 machine to the C drive, other hard drives work fine. Also on the 7 machine you cannot see the XP machine, but typing in the IP on 7 you can share folders and files no problem. Now if only I could get network printing to work. Each time I 7 cannot find a driver and wont install it. is there anyway to find drivers separately I couldn't find any vista drivers on the canon website, they said they were part of windows update but 7 doesnt check windows update for drivers...

Windows 7 does check windows update for drivers, that is where i got drivers for my networked printer. Cannon or another site should have your drivers if windows update does not.

Well it doesnt seem to for me. How did you install your networked printer? I tried either going connect after finding it by IP address. It tells me it doesnt have a driver and asks for CD. The other way is using the add printer wizard and by adding by IP. this installs the driver but hangs whenever I go to print. it displays "connecting printer status" until i cancel the job

Somm said:

Well it doesnt seem to for me. How did you install your networked printer? I tried either going connect after finding it by IP address. It tells me it doesnt have a driver and asks for CD. The other way is using the add printer wizard and by adding by IP. this installs the driver but hangs whenever I go to print. it displays "connecting printer status" until i cancel the job

The printer i have does not have network capability it is a usb printer shared from another machine on the network, it was added with the printer wizard and using the UNC path since it is on an XP machine which can not be browsed.