David,

Thanks for getting on this significant issue.  It's too bad that VMWare and Apple can't be in better sync on these things - this is kind of a major bug to miss when debugging the software, especially when "driverless printing" is pushed as a major feature of the Fusion software.

I have a few points to make that I hope VMWare takes constructively:

1.  How does such a major bug NOT get weeded out during beta testing of the upgrade?  Driverless printing is a major feature of the software that is occuring with the only OS on which Fusion is supposed to be able to run.

2.  I personally don't think "reinstalling OS X 10.5.6" is a good workaround.  Many of your customers are folks who go to the mall and buy their iMac or Macbook from the Apple Store, and then install your software to be able to keep using some Windows apps.  They don't know from reinstalling OS's or kernel dumps, etc. - they just want their computer to work.  Apple is no help either - I've asked the "genius's" and they're not interested in third party software.

3.  Several here have complained about VMWare's practice of free support ONLY for 30 days after the original purchase.  As is clear here, if the software breaks after that time, VMWare wants money for support.  I propose that, going forward, if bugs like this can't be caught during beta testing, that VMWare consider offering free support for paying customers when major bugs like this emerge after a factory update is issued.  Alternately, we need a clear path to make these issues known and get action quickly.  

Here's hoping the real fix comes soon.

Thanks.

etung

Thanks for the reply.  I'm sure you'll understand a fair amount of frustration is built into the comments here.  However, as end users of software, we are constantly shuttled between software vendors when problems happen like this.  The OS guys blames it on the apps guy, and vice versa.  In the meantime, we are left with broken software we can't use properly, and only forums like this in which we can seek solutions.

If you find a solution quickly to fix this and issue another update, that would be great.  In the meantime, understand that all we end users want from software we buy is that at least most of the major features work as advertised.

I see that you all feel as strongly as I do on this issue.  Given that you point out the security update came out after 2.02 Fusion did, I understand your frustration with the issue.

My frustration is as an end user that this has to happen.  I wish to fix the problem, not the blame.   I too wish Apple would test their updates using all available popular apps software before their release, especially since they sell Fusion on their website, just as much as I wish that apps software could be bullet proof to any OS changes.  Believe me.....I've gone through enough with a popular antivirus/security software package on Windows to fill several forums.

I hope you can fix the printer issue soon.

stevesp64 wrote:

So, what is the workaround if you need to print to a network printer, but your network will not work in bridged mode?  My company has a 1 ip address per port configuration, this is a security feature, so my mac gets the IP address and windows gets nothing, therefore the VM can't talk to the network, hence the network printers are unavailable.

 

 

Please let me know asap, my manager doesn't like the "Fusion is broken because VMWare and Apple can't play nice" excuse for why I am not getting my work done.

1. Set the target Virtual Machine's Network to NAT and if running when you change it then release/renew its IP Address and if you don't know how then reboot the Virtual Machine or make the change when it's off to begin with.

2. Uncheck the Enabled check box under Printers in the target Virtual Machine's Settings.

2. Turn on Printer Sharing in OS X and enable the target Printer to be shared.

3. In Windows add a new Printer and add it as a Network Printer using the following URL Convention.

http://Computer_Name:631/printers/Queue_Name_of_target_Printer

Or

http://Host_vmnet8_IP_Address:631/printers/Queue_Name_of_target_Printer

Examples:

On my MacBook Pro the Network Attached Shared Printer is an HP LaserJet 4050N and the following information is relevant to this.

Computer_Name = MacBookPro

Host_vmnet8_IP_Address = 192.168.51.1

Queue_Name_of_target_Printer = HP_LaserJet_4050

So either of the following examples works in my Windows XP Virtual Machine.

http://MacBookPro:631/printers/HP_LaserJet_4050

http://192.168.51.1:631/printers/HP_LaserJet_4050

davidliu wrote:

Thanks Woody for the detailed instructions. The same is also documented in the video link in my original post (with my latest edits). Edit: here is the link again: http://tr.im/gwi2

No problem.   I always forget about the videos (probably because I don't need them) but I also have foun from the past when I used to point usare to the printer video many of then still need written directions.

Steve, the reason we say use Bridged network is because so that auto discovery works and you do not have to go through these manual process. In your case, follow Woody's steps and you should get it to work in NAT mode.

Steve, I will add that when you go to add the printer in this manner that if the manufacture doesn't have a PostScript Printer Driver for your Model then you can use an Apple LaserWriter PS drive in its place.  (That may be in the video although I haven't watched it in over a year and haven't watched the Fusion 2 version.

I have been experiencing the same printer (thinprint) issue.  I have tried the various work arounds including OSX archive and install to 10.5.4 (which removed the latest security update.  None worked .  I then decided to uninstall fusion 2.02 and reintal 2.01.  Print through works like a charm.

Conclusion?  2.02 apparently has a problem with print through OSX and the security update isn't the issue.