twocanoes.com

Winclone Support :: RE: Mac Pro -->> MacBook Pro -> no trackpad, no USB mou

Author: tperfitt
Posted: Thu Aug 07, 2008 3:37 pm (GMT -7)
Topic Replies: 1

Did you try this?

http://www.twocanoes.com/forums/viewtopic.php?p=3304

tim

Winclone Support :: RE: My disk image is borked - file extension?

Author: tperfitt
Posted: Thu Aug 07, 2008 3:35 pm (GMT -7)
Topic Replies: 1

If you right-click (control click) on the winclone image, and select Show Package Contents, what files do you see?

tim

Winclone Support :: RE: Restoring a Windows image to another machine

Author: tperfitt
Posted: Thu Aug 07, 2008 3:33 pm (GMT -7)
Topic Replies: 7

Great! Thanks for using Winclone!

tim

Winclone Support :: RE: Winclone Errors out at 81%

Author: tperfitt
Posted: Thu Aug 07, 2008 3:33 pm (GMT -7)
Topic Replies: 3

Please post the top of the Winclone log that shows the disk information, and it should help determine the format of the drives. Better yet, compress ~/Library/Logs/Winclone.log and send it to support@twocanoes.com

tim

Winclone Support :: RE: Restored and Windows partitions show too large, can't boot

Author: tperfitt
Posted: Thu Aug 07, 2008 3:31 pm (GMT -7)
Topic Replies: 3

The partition map looks fine:

#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *232.9 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Macintosh HD 151.9 Gi disk0s2
3: Microsoft Basic Data BOOTCAMP 80.7 Gi disk0s3

Partition 0 is the whole disk, and it is ~ 250 GB. Partition 1 is a special 200 MB EPFI partition used in the GUID partition map, and the Mac side is 152 GB, and the Windows side is ~81GB. All looks good. The log also show that it restored correctly, and that the generic BCD was copied correctly.

Do you have any 3rd party utilities like Paragon installed for NTFS read/write support?

Try disconnecting all the other external devices. Also, does the Windows partition show up in Mac OS X? Does the Windows partition show up in Startup Disk?

tim

Winclone Support :: RE: Shrunk NTFS, Size still reporting partition size

Author: tperfitt
Posted: Thu Aug 07, 2008 3:22 pm (GMT -7)
Topic Replies: 4

Do the errors happen when you run winclone.perl, or during the netrestore restore?

tim

Winclone Support :: RE: Vista BSODs after cloning onto larger drive

Author: tperfitt
Posted: Thu Aug 07, 2008 3:20 pm (GMT -7)
Topic Replies: 1

Try safe boot, and see if windows boots up. Did you use the "use generic BCD" option in preferences? That helps with boot issues in Vista. Does it show up correctly on the Mac OS X side?

Post the log of Winclone (~/Library/Logs/Winclone.log) or compress it and send it to support@twocanoes.com.

If it is the same machine but different hard drive, i am surprised it doesn't just work. How did you create the Windows partition?

tim

Winclone Support :: Mac Pro -->> MacBook Pro -> no trackpad, no USB mou

Author: SteveDarden
Subject: Mac Pro -->> MacBook Pro -> no trackpad, no USB mou
Posted: Thu Aug 07, 2008 12:04 pm (GMT -7)
Topic Replies: 1

From studying other forum traffic on this I know I'm not the first to discover this problem. My symptoms are a bit different.

Mac Pro and MacBook Pro are both 10.5.4. XP SP2 on Mac Pro separate bootcamp volume. I used Winclone to shrink the NTFS partition from 54GB down to 19GB, then imaged/restored the smaller volume to a 22GB partition on the MacBook Pro.

Which boots fine into XP but for the no trackpad, and no USB mouse support. The external mouse was a surprise - tried my Microsoft optical mouse.

I tried to reinstall "Boot camp drivers" twice, first using retail Leopard 1.5.1, second using the MBP Leopard 1.5.0. Both intallers autorun OK, startup but "hang" at "Status: Apple Built-in iSight".

Any suggestions much appreciated!

Winclone Support :: Vista BSODs after cloning onto larger drive

Author: 00z3r0
Subject: Vista BSODs after cloning onto larger drive
Posted: Thu Aug 07, 2008 8:23 am (GMT -7)
Topic Replies: 1

Hello,

My boss needed to have his OS 10.5 + Vista Bootcamp partition transferred from his original MacBook Pro drive to a new, larger drive. I had previously partitioned the new drive to have 200GB reserved for the Mac OS side, and the rest (120GB) for Bootcamp.

I used NetRestore to transfer the Mac side, and it boots fine. The Bootcamp partition was left blank until after the new drive was installed. I then took the original drive, installed it into a FireWire 800 enclosure, which attached to my Mac Pro, and used WinClone to make an image of the Vista partition. This completed without errors. I then transferred the WinClone image over to the MBP via FireWire Target Disk Mode.

I then booted into the Mac partition of the MBP, fired up WinClone, and told it to restore the image I made to the MBP's Bootcamp partition. This all went without a hitch, and took about an hour and change to restore. The log said that the operation completed successfully. I then told WinClone to expand the NTFS partition so that the Vista installation used all the space on the partition. This also completed without errors.

The problem now is that when I try to boot into the Vista installation on the new drive, it starts to load everything, and then BSODs and reboots very quickly ad nauseam.

My boss did not want anything "destructive" done to the original drive, so no Syspreping or pre-cloning work was done to the original drive. I didn't think it was necessary to Sysprep the original installation anyway, since the installation isn't going onto a new motherboard.

What could be going wrong, or what should I do? Please advise, as my boss is getting very upset that his laptop is not functional under Bootcamp. :-/

EDIT: Is is possible to reinstall the old drive and still have Vista boot off of it without BSODing?

Thank you!

Winclone Support :: My disk image is borked - file extension?

Author: johnselekta
Subject: My disk image is borked - file extension?
Posted: Thu Aug 07, 2008 7:47 am (GMT -7)
Topic Replies: 1

Hi

I imaged my XP partition with Winclone ahead of a hard drive upgrade - my mac partition came back fine but the windows one won't show up now.

I made the mistake of renaming the image to end with .DMG so I could retrieve some files from it, but now I can't restore it in Winclone.

If i rename the image file extension to .winclone I can then get to it for a restore, but the image size is 'unknown' and the file type is 'special'.
Then when I hit 'restore' it says 'invalid image: image file not found'.

What is the file extension meant to be, .winclone? How would I go about restoring this to my partition? Please help, I'm XP-less!!

thx

Winclone Support :: RE: Restoring a Windows image to another machine

Author: hjj979
Posted: Thu Aug 07, 2008 5:12 am (GMT -7)
Topic Replies: 7

Yes that did the trick. Thank you very much for your assistance.

Winclone Support :: RE: Winclone Errors out at 81%

Author: idle0095
Posted: Wed Aug 06, 2008 6:38 pm (GMT -7)
Topic Replies: 3

well how do i make it smaller then 4 gb then? this is so confusing. the disk im saving it to is the same format as the main mac hd. im saving it to a usb mac hd fromatted the same way as the main mac hd. so what do i do here to fix this issue?

Winclone Support :: RE: Restored and Windows partitions show too large, can't boot

Author: iBrent
Posted: Wed Aug 06, 2008 6:37 pm (GMT -7)
Topic Replies: 3

Here is the log file for the last attempt I made. Originally I had been restoring from the external HD I mentioned above. At this point I had copied the .winclone file to the desktop and was restoring from there. This is with the BCD file removed from the image file (I had tried it with the original BCD, and saw in one post to try taking out the BCD, and the results were the same):

Thanks,

iBrent

Winclone Support :: RE: Shrunk NTFS, Size still reporting partition size

Author: mperbix01
Posted: Wed Aug 06, 2008 5:17 pm (GMT -7)
Topic Replies: 4

Sure will, I will try it from work tomorrow and post the errors....but it seems that NetRestore was missing some Perl binaries.....

-Mike

Winclone Support :: RE: Winclone Errors out at 81%

Author: tperfitt
Posted: Wed Aug 06, 2008 4:43 pm (GMT -7)
Topic Replies: 3

This is usually due to either saving the image to a drive that is full, or if the drive is FAT32 and the file is getting > 4 GB.

tim