Transferring a file from Mac to Windows

[Shaw]

Incidentally the only reason why Macs can't write to NTFS is because Microsoft has refused licensing to allow it.

Like OSX?

Actually Apple has worked quite hard to keep things like that open in Mac OS X.

By contrast, Microsoft has fought tooth and nail to keep others at a disadvantage when any of their products are in the mix. They have hidden APIs from developers of other Windows applications to make sure that Microsoft applications have the advantage on Windows. They have hidden aspects of their networking protocols to make sure that other platforms can't interact with Windows systems on networks (Samba's development team has been fighting this for years).

Apple has never hidden such aspects of Mac OS X. So no, not like OSX.

 

[Jimilu]

I just transfer a 14 gb file from my macbook to my dell xps through my home network.
Just enable file sharing and ftp in the mac. I recommend to connect the mac and pc through a Ethernet cable and a router because it is much faster. The on the pc, open explorer and write the ip on the mac (i.e. ftp://192.168.1.100) and the login as. Use your login and password from the mac and voila! you can tranfer any file. If you want to transfer form a external hard drive, you can use a ftp client.

 

[Lindley]

That's what I mean. Macs are crap. You need expensive software do to something very basic it cannot do out of the box. Especially unnerving since these things are lauded as more user friendly that Windows...

Are you still struggling, or did your "expensive software required" turn out to be nothing more than a failure to check the help files?

The tools you know always seem simpler at first.

 

[Chess Piece Face]

That's what I mean. Macs are crap. You need expensive software do to something very basic it cannot do out of the box.

No you don't. You clearly don't know what you are talking about, which is a clue that everyone can pretty much ignore everything you say about Macs and PCs from now on.

Thanks!

 

[Amaris]

The only software I have purchased for my Mac was iLife '08 (when I got the iMac the choice was Leopard or iLife '08. I think I made the right choice), and I got it for $50. Everything else has been available as open source freeware, and it all integrates beautifully! I am still impressed with this machine, and I learn something new every day.


J.

 

[BCI]

That's what I mean. Macs are crap. You need expensive software do to something very basic it cannot do out of the box. Especially unnerving since these things are lauded as more user friendly that Windows...

Are you still struggling, or did your "expensive software required" turn out to be nothing more than a failure to check the help files?

The tools you know always seem simpler at first.

How helpful!

 

[BCI]

That's what I mean. Macs are crap. You need expensive software do to something very basic it cannot do out of the box.

No you don't. You clearly don't know what you are talking about, which is a clue that everyone can pretty much ignore everything you say about Macs and PCs from now on.

Thanks!

I spent several hours trying to make it work. I want to connect to the Mac from several Windows computers. The help says I have to create (on the Mac) a user for each Windows machine, for each Windows user, that wants to access the Mac.

 

[Amaris]

That's what I mean. Macs are crap. You need expensive software do to something very basic it cannot do out of the box.

No you don't. You clearly don't know what you are talking about, which is a clue that everyone can pretty much ignore everything you say about Macs and PCs from now on.

Thanks!

I spent several hours trying to make it work. I want to connect to the Mac from several Windows computers. The help says I have to create (on the Mac) a user for each Windows machine, for each Windows user, that wants to access the Mac.

I plugged in my Mac, turned on Airport, and every Windows machine on the network picks it up. Through Samba (Go>Connect to Server>Windows Machine), I connected in seconds and can transfer files back and forth. Really, it was very simple. PC to Mac, Mac to PC. Easy as pie.

J.

 

[Lindley]

I spent several hours trying to make it work. I want to connect to the Mac from several Windows computers. The help says I have to create (on the Mac) a user for each Windows machine, for each Windows user, that wants to access the Mac.

Which help topic was that? I could see needing to create *one* additional user, maybe, if there was some setting you had to toggle. But I can't imagine why one for each machine would be needed.

How helpful!

Hey, a bunch of suggestions have been given. We can't really tell you more until you've related which ones worked and which ones didn't.

 

[Candlelight]

MacFuse with the NTFS-3G drivers will allow Mac OS X to write to NTFS formatted volumes. It's free.

HFSEXplorer should allow Windows to read and write to an HFS(+) formatted volume. It is also free, but more cumbersome than MacDrive.

They are very cool, have installed both but will try them later today.

 

[Captain Intrepid]

That's what I mean. Macs are crap. You need expensive software do to something very basic it cannot do out of the box. Especially unnerving since these things are lauded as more user friendly that Windows...

Are you still struggling, or did your "expensive software required" turn out to be nothing more than a failure to check the help files?

The tools you know always seem simpler at first.

Well, most computer problems are wetware issues.

 

[TerriO]

Or try this. Macdrive. You install it on the windows side and you should be able to transfer both ways...

http://rapidshare.com/files/187338659/MacDrive7.2.5-keygen.rar

That would be absolutely perfect however I'm actually on a work machine so I can't download a cracked version. Thanks anyway!

To everyone that have helped, thanks, but I've found another machine which I can store my VM image on, so all is settled.

Discussions of cracked software...bad.

Let's please leave such discussions to the hacker boards where they belong. Thanks.

 

[Hedbergian]

MacFuse with the NTFS-3G drivers will allow Mac OS X to write to NTFS formatted volumes. It's free.

This, for me, was the best solution to read/write on my Boot Camp volume through OS-X finder. Remember, you'll need x-code in order to compile macfuse.

 

[BCI]

I plugged in my Mac, turned on Airport, and every Windows machine on the network picks it up. Through Samba (Go>Connect to Server>Windows Machine), I connected in seconds and can transfer files back and forth. Really, it was very simple. PC to Mac, Mac to PC. Easy as pie.

J.

Does not work. Your instructions describe how to connect to Windows from Mac, not the other way around.

As for the other tips: There is no SMB share in the options. I have activated "Windows share", but it does not work. Entering the address (as suggested) on a windows machine in explorer does nothing.

FTP does work. But: I have to enter the Macs password on the Windows computer. That's not what I call secure. That's just horrible. I want read/write access to one folder, nothing more. Windows grants that without password. But, better than nothing...

 

[Amaris]

I plugged in my Mac, turned on Airport, and every Windows machine on the network picks it up. Through Samba (Go>Connect to Server>Windows Machine), I connected in seconds and can transfer files back and forth. Really, it was very simple. PC to Mac, Mac to PC. Easy as pie.

J.

Does not work. Your instructions describe how to connect to Windows from Mac, not the other way around.

As for the other tips: There is no SMB share in the options. I have activated "Windows share", but it does not work. Entering the address (as suggested) on a windows machine in explorer does nothing.

FTP does work. But: I have to enter the Macs password on the Windows computer. That's not what I call secure. That's just horrible. I want read/write access to one folder, nothing more. Windows grants that without password. But, better than nothing...

Windows XP detected the Mac on the network after I changed the Mac's Workgroup to: WORKGROUP. Vista did likewise. It only took a minute to do.

SYSTEM PREFERENCES>NETWORK>ADVANCED>WINS>Type in WORKGROUP and then click Apply.

Done. XP & Vista should pick up your Mac on the network if it didn't already.

J.

 

[Lindley]

As for the other tips: There is no SMB share in the options. I have activated "Windows share", but it does not work.

What OS is the Mac running? That sounds like you may have Tiger (10.4), when most of these suggestions have been directed at Leopard (10.5).

 

[BCI]

10.4, exactly. (With 10.3 the Mac would not connect to Windows machines at all; the mouse in finder would start spinning and never stopped.)

 

[Lindley]

I don't have any experience with that; but a Google did turn up this article:
http://support.apple.com/kb/HT1568

which you might give a try.

 

[BCI]

Step by step... I went to the Directory services, checked the SMB options, and set up the correct name of the workgroup. Then I entered the computer/user name in Windows explorer. After entering login and password I can now access the Mac.

I still have complaints... it shows the entire user directory, yet just the "Public" folder would have been enough. And again, the thing with the password. Can't I have just one folder free for all?

 

[Lindley]

Without following your step-by-steps I can't say. However, generally logging in as a Guest will give you public-folder access only; using a username and password gives you access to that user's entire folder. More if it's an admin account.

I'm not positive if that works the same way over a Samba connection. There are always limitations to the abilities of protocols other than a system's native method, especially in older OSes.