Searching \ for '[PIC] VMWare Fusion and XP on OS-X' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: massmind.org/techref/microchip/devices.htm?key=pic
Search entire site for: 'VMWare Fusion and XP on OS-X'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] VMWare Fusion and XP on OS-X'
2009\02\16@005719 by Joseph Bento

face
flavicon
face
Many thanks to all that recommended VMWare Fusion to run XP as a  
virtual machine on my MacBook.  Parallels had caused many problems,  
especially since I upgraded to Parallels 4.

I installed VMWare today, and reinstalled XP.

The XP install was not without issues, however.  Seems I installed my  
copy one too many times, even though the only place that copy has ever  
been used was on this MacBook.  I had to call MS Support and go  
through their automated system, answering lots of questions, and  
finally receiving a new activation code.  I eventually want to upgrade  
the HD in this MacBook, and only hope the cloning software also moves  
the virtual machine without issue.  I don't want to go through that  
telephone activation hassle again.

Anyhow, all my programming tools seem to work properly now in a  
Windows virtual machine with WMWare.  Parallels had too many issues  
with the USB port.  Really a shame to have spent so much for software,  
only to find it ultimately doesn't meet your needs.  I'll have to fork  
out another $79 for VMWare in a month when the trial license expires.

Joe

2009\02\16@125756 by Marc Nicholas

picon face
Glad to hear things worked out. I really have been pretty happy with
Fusion and my programming tools (Swordfish and a PICKit 2).

One nice touch with Fusion is that it now comes with a 1-year license
to McAffee....maybe that will lessen the pain?

-marc


On Mon, Feb 16, 2009 at 12:56 AM, Joseph Bento <spam_OUTjosephTakeThisOuTspamkirtland.com> wrote:
{Quote hidden}

> -

2009\02\16@143121 by Gerhard Fiedler

picon face
Joseph Bento wrote:

> The XP install was not without issues, however.  Seems I installed my
> copy one too many times, even though the only place that copy has
> ever been used was on this MacBook.  

XP doesn't ever see your MacBook; all it sees is the VM you are
installing it in (and its virtual hardware). The XP activation tracks
the hardware XP sees -- which is not your MacBook, but the VM where
you're installing XP.

> I eventually want to upgrade the HD in this MacBook, and only hope the
> cloning software also moves the virtual machine without issue.  

A VM is nothing more than a set of files that is properly registered
with the program that can "play" the VM. So if you make sure that you
copy over all the relevant files, you'll have your VM on your new disk.
If for some reason the registration of this VM with your VM "player"
(seems to be VMware Fusion) doesn't copy over, you can register it and
it should work normally. People exchange VMs between different systems
all the time.

Gerhard

2009\02\16@153652 by Tamas Rudnai

face picon face
On Mon, Feb 16, 2009 at 7:30 PM, Gerhard Fiedler <.....listsKILLspamspam@spam@connectionbrazil.com
> wrote:

> XP doesn't ever see your MacBook; all it sees is the VM you are
> installing it in (and its virtual hardware). The XP activation tracks
> the hardware XP sees -- which is not your MacBook, but the VM where
> you're installing XP.
>

True, however, VmWare changes the emulated hardware in different versions,
so the guest OS still could see some difficulties. BTW: Norton Ghost is
capable of tweeking the activation key so that you can make a ghost image on
your hardware and reghosting it on another without minding the activation
process. Also pirates are using the enterprise version which doe snot have
this activation game on it, so I really do not understand Microsoft why do
they bother legitimate users with this...

Tamas
--
Rudonix DoubleSaver
http://www.rudonix.com

2009\02\19@124857 by Alden Hart

flavicon
face
Pardon the late response, but you might consider getting your entire XP
and dev environment set up and getting it right then backing up the
/Documents/Virtual Machines/Windows XP <whatever> file to some external
drive.

One reason is to is to avoid problems in the hard drive upgrade you
spoke about, but more importantly you can avoid (or at least roll back)
"Windows bloat" this way. My virgin images weigh in about 4 GB. I've
seen them grow to almost 20 GB over time! There were no other changes to
account for this bloat. No new SW installed, and all my working files
are on the Mac shared drive (not in the C: drive which is part of the VM
image.) So I rolled it back.

Lastly, if your mac should ever bomb on you while a VM is open it can do
some nasty things to the XP image - and you'll really want that virgin
image.

Alden



Gerhard Fiedler wrote:
{Quote hidden}

2009\02\19@194252 by Joseph Bento

face
flavicon
face

On Feb 19, 2009, at 10:48 AM, Alden Hart wrote:

> Pardon the late response, but you might consider getting your entire  
> XP
> and dev environment set up and getting it right then backing up the
> /Documents/Virtual Machines/Windows XP <whatever> file to some  
> external
> drive.
>

Thank you for the info.  I hadn't considered this.  I do have my  
virtual machine set up perfectly now, without any excess bloat.  XP is  
installed, MPLAB with registered C compilers, and other programming  
tools.  The image file has been saved to my external backup drive, and  
set as not to be accidentally overwritten.

Joe


2009\02\19@212618 by Marc Nicholas

picon face
Do a Snapshot!

-marc

On Thu, Feb 19, 2009 at 7:42 PM, Joseph Bento <josephspamKILLspamkirtland.com> wrote:
{Quote hidden}

> -

2009\02\21@110828 by Joseph Bento

face
flavicon
face

On Feb 15, 2009, at 10:56 PM, Joseph Bento wrote:

> Many thanks to all that recommended VMWare Fusion to run XP as a
> virtual machine on my MacBook.  Parallels had caused many problems,
> especially since I upgraded to Parallels 4.


I may have spoke too soon in my praises of VMWare on my Mac.

I imagine with any virtual machine there are obstacles to overcome.

My Pickit2 now works properly in a virtual machine.

The Keyspan serial adaptor connected to a Wisp648 programmer does  
not.  The Wisp software returns all sorts of errors running on the  
virtual machine, while it runs perfectly on a native windows box with  
the same Keyspan and Wisp648 programmer.  The Wisp software (in its  
native Python code), Keyspan, and the 648 programmer run perfectly in  
a OS-X (Unix) window.

The failures on the virtual machine exist when wisp is called from  
JALEdit or commands entered in a terminal box.  The hex file does  
appear to write, but then there is a verification that fails.  The  
program in the chip is then corrupt, and the Wisp648 programmer  
displays an error through its on-board LED.

I just thought I'd pass along some observations.  There may or may not  
be a fix to use this hardware in a virtual machine, but I'm unaware of  
what to try.


Joe

2009\02\21@122709 by Nate Duehr

face
flavicon
face

On Feb 21, 2009, at 9:07 AM, Joseph Bento wrote:

> I imagine with any virtual machine there are obstacles to overcome.

Yeah, the whole virtual machine is an obstacle, in this case.  :-)

Especially when the OS can run natively on the hardware.

BootCamp, here you come!  (GRIN)

Nate

2009\02\21@141158 by Marc Nicholas

picon face
That's a known issue AFAIK.

Some people have reported on the VMware communities that a Prolific
chipset seems to work better:

http://communities.vmware.com/thread/135399;jsessionid=1B49FBE58211395F6B7AC026E68BB461?start=15&tstart=0

-marc

On Sat, Feb 21, 2009 at 11:07 AM, Joseph Bento <.....josephKILLspamspam.....kirtland.com> wrote:
{Quote hidden}

> -

2009\02\21@142206 by Wouter van Ooijen

face picon face
Joseph Bento wrote:
> There may or may not  
> be a fix to use this hardware in a virtual machine, but I'm unaware of  
> what to try.

Listing the exact "all sorts of errors" might be a start.


--

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu

2009\02\21@142433 by Bob Blick

face
flavicon
face
Joseph Bento wrote:

> The Keyspan serial adaptor connected to a Wisp648 programmer does  
> not.  

Hi Joe,

You might try a no-frills serial adapter. Keyspans are very fancy, which
is nice, but it makes them unpopular so probably not as well supported
as one of the <$10 cheapies.

You must really love that MacBook by now :(

Cheerful regards,

Bob

2009\02\21@163056 by Joseph Bento

face
flavicon
face

On Feb 21, 2009, at 12:21 PM, Wouter van Ooijen wrote:

> Joseph Bento wrote:
>> There may or may not
>> be a fix to use this hardware in a virtual machine, but I'm unaware  
>> of
>> what to try.
>
> Listing the exact "all sorts of errors" might be a start.

Hi Wouter,

Yes, listing the errors would likely help.  I was not in a position to  
list everything at the time.

Here's a screen capture:

C:\PICjal\xwisp2>xwisp2w port 3 go c:\jallib\16f690\blink.hex
 xwisp2 version 1.9.5 for Windows (Jan 24 2008, Open Watcom C/C++ 1.70)
File c:\jallib\16f690\blink.hex loaded and is Intel Hex format  
conforming
More bytes received (2) than expected!
Detected programmer: Wisp628, firmware version 1.27
Target: 16F690 revision 05 (ID=1405)
Target erased
Transferring program to 16F690 via Wisp628
Transferring program memory...100%
Verifying program memory......  0%failed at 000008, expected: '01A3',  
found: '3F
FF'
Write-Verify operation failed after 0.30 seconds, rc 21
xwisp2 failed after 1.92 seconds, rc 21
Press 'Enter' to continue:


C:\PICjal\xwisp2>

Someone commented on using a simpler USB/serial adaptor.  I have had  
worse results with plain adaptors, in that they would not work  
properly with my ham radio related stuff in a native windows  
environment, nor would OS-X recognize them.    The Keyspan previously  
worked in Parallels before Parallels flaked.  For most of my work, I  
love the Mac.  If I were more comfortable at a command line, I could  
do all my PIC learning and development on the Mac.  I hadn't wanted to  
resort to bootcamp, but that might be my best option.

Joe



2009\02\21@163347 by Joseph Bento

face
flavicon
face

On Feb 21, 2009, at 12:11 PM, Marc Nicholas wrote:

> That's a known issue AFAIK.
>
> Some people have reported on the VMware communities that a Prolific
> chipset seems to work better:
>
> http://communities.vmware.com/thread/135399;jsessionid=1B49FBE58211395F6B7AC026E68BB461?start=15&tstart=0

Thanks for the link.  It certainly takes awhile for a fix, especially  
since the issue was known four years ago.

Joe

2009\02\22@034647 by Wouter van Ooijen

face picon face
> C:\PICjal\xwisp2>xwisp2w port 3 go c:\jallib\16f690\blink.hex

Thanx, but I see you use xwisp2w, which is not mine (and I don't know it
very well).

But it is very strange that the communications seems to be OK, but the
programming (or verify) fails.

--

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu

2009\02\22@141820 by Joseph Bento

face
flavicon
face

On Feb 22, 2009, at 1:45 AM, Wouter van Ooijen wrote:

>> C:\PICjal\xwisp2>xwisp2w port 3 go c:\jallib\16f690\blink.hex
>
> Thanx, but I see you use xwisp2w, which is not mine (and I don't  
> know it
> very well).

I wasn't aware this wasn't yours.  I'll download a copy directly from  
your web page and report back.  :-)
>
> But it is very strange that the communications seems to be OK, but the
> programming (or verify) fails.

Yes.  As I mentioned, everything works perfectly from a OS-X terminal  
box.

bash-3.2$ xw go 16f690_blink.hex
XWisp 1.30, command line mode
hardware: Wisp628 1.27 (fast) (wisp648 firmware)
target: 16f690, device code 1400 revision bits 05
OK
bash-3.2$

"xw" is just an executable script:
python ~/Prog_JAL/Wisp/xwisp_src/xwisp.py port /dev/tty.KeySerial1 $*

So I do know there is nothing wrong with the hardware itself.  I did  
find online where many others have had issues with the Keyspan in a  
VMWare Virtual session.   I tried a no-name Radio Shack USB-Serial  
adaptor, and the results were no different.  Both the Keyspan and  
RadioShack adaptors work perfectly in a native Windows environment.    
I guess Bootcamp is my best option.  GRRRRR....

Joe

More... (looser matching)
- Last day of these posts
- In 2009 , 2010 only
- Today
- New search...