Moving TM drive

I am currently using a 2TB drive in an external SATA 3 enclosure as a Time Machine disk for my Mac Pro 10.6.8. The disk has two partitions, one to back up my 250GB SSD startup drive and one to back up my 500GB data drive. Since my Mac Pro sometimes loses connection with the eSATA enclosure I have decided to remove that partitioned Time Machine drive into the Mac Pro's remaining free internal drive bay. So far I have Time Machine backing up only my boot disk to the TM drive but I plan on having it back up my Data disk on the backup drive's other (presently clean) partition once I relocate the drive into my Mac Pro. Two questions: 1) Will Time Machine recognize the transplanted drive and it's existing Time Machine file right off the bat? 2) In 10.6.8 can I have Time Machine back up two internal drives separately to two partitions on an internal Time Machine drive?
Thanks in advance for any insights.

BIGDADDY30,
You can connect the Time Machine drive to your Mac Pro just fine. It doesn't need to be erased first, and there may be several reasons why you wouldn't want to erase it, at least for a while.
You mention that you purchased the Mac Pro "recently." I assume that this means you are currently using it, and any files from your Powerbook that you might want or need have been transferred over. Correct? In other words, there is no reason to continue storing the files contained in the (old) Time Machine backup. Correct?
You can use the external drive for Time Machine on the Mac Pro, and in fact you will be asked if you want to use it that way the first time you connect it. However, it must be erased, and further, repartitioned in order to use it with Time Machine on the Mac Pro.
You see, Time Machine on a PPC (G4) Mac must have a backup drive that uses the "Apple Partition Map," while Time Machine on an Intel Mac needs one with the "GUID" partition map.
When you connect it to your Mac Pro, dismiss the option to use it immediately for TIme Machine. Open DIsk Utility, select the drive in the list on the left select the drive, not the named volume that will appear indented below), then click the "Partition" tab. Choose a single partition, set the format for that one partition to "Mac OS Extended (journaled)," then click the "Options..." button. You'll want to choose the "GUID" partition map here. Confirm your choice, then click "Apply."
You can then choose the drive for Time Machine's use.
Scott

Similar Messages

Failed boot after moving hard drive (IDE not SATA)

Greetings all.
I am attempting to setup a headless box, and in doing so I am installing Arch on one system (Sapphire Axion A3-M275 Motherboard), then moving the hard drive to the new system (SGS1660, a VIA CLE266/VT8235 based headless rack-solution). After moving the drive into the SGS1660, the system fails to boot. Attached output from the Serial Console:
Booting 'Arch Linux'
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz26 root=/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b r
o console=ttyS0,115200
[Linux-bzImage, setup=0x3600, size=0x1ad6d0]
initrd /kernel26.img
[Linux-initrd @ 0x2ff21000, 0x9e7a5 bytes]
Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.0 20090630 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Jul 20 11:20:32 UTC 2009
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
NSC Geode by NSC
Cyrix CyrixInstead
Centaur CentaurHauls
Transmeta GenuineTMx86
Transmeta TransmetaCPU
UMC UMC UMC UMC
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000002ffd0000 (usable)
BIOS-e820: 000000002ffd0000 - 000000002ffde000 (ACPI data)
BIOS-e820: 000000002ffde000 - 0000000030000000 (ACPI NVS)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
DMI 2.3 present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
last_pfn = 0x2ffd0 max_arch_pfn = 0x100000
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Scanning 0 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009fc00 (usable)
modified: 000000000009fc00 - 00000000000a0000 (reserved)
modified: 00000000000e0000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 000000002ffd0000 (usable)
modified: 000000002ffd0000 - 000000002ffde000 (ACPI data)
modified: 000000002ffde000 - 0000000030000000 (ACPI NVS)
modified: 00000000fec00000 - 00000000fec01000 (reserved)
modified: 00000000ff780000 - 0000000100000000 (reserved)
init_memory_mapping: 0000000000000000-000000002ffd0000
RAMDISK: 2ff21000 - 2ffbf7a5
ACPI: RSDP 000f6ad0 00014 (v00 ACPIAM)
ACPI: RSDT 2ffd0000 0002C (v01 A M I OEMRSDT 09000521 MSFT 00000097)
ACPI: FACP 2ffd0200 00084 (v02 A M I OEMFACP 09000521 MSFT 00000097)
ACPI: DSDT 2ffd0390 03270 (v01 MiniV MiniV080 00000080 INTL 02002026)
ACPI: FACS 2ffde000 00040
ACPI: OEMB 2ffde040 00046 (v01 A M I AMI_OEM 09000521 MSFT 00000097)
0MB HIGHMEM available.
767MB LOWMEM available.
mapped low ram: 0 - 2ffd0000
low ram: 0 - 2ffd0000
node 0 low ram: 00000000 - 2ffd0000
node 0 bootmap 00011000 - 00016ffc
(9 early reservations) ==> bootmem [0000000000 - 002ffd0000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
#2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
#3 [0000100000 - 0000626e44] TEXT DATA BSS ==> [0000100000 - 0000626e44]
#4 [002ff21000 - 002ffbf7a5] RAMDISK ==> [002ff21000 - 002ffbf7a5]
#5 [0000099c00 - 0000100000] BIOS reserved ==> [0000099c00 - 0000100000]
#6 [0000627000 - 0000629230] BRK ==> [0000627000 - 0000629230]
#7 [0000010000 - 0000011000] PGTABLE ==> [0000010000 - 0000011000]
#8 [0000011000 - 0000017000] BOOTMAP ==> [0000011000 - 0000017000]
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
Normal 0x00001000 -> 0x0002ffd0
HighMem 0x0002ffd0 -> 0x0002ffd0
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x0002ffd0
Using APIC driver default
ACPI: PM-Timer IO Port: 0x808
SMP: Allowing 1 CPUs, 0 hotplug CPUs
No local APIC present or hardware disabled
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
Allocating PCI resources starting at 40000000 (gap: 30000000:cec00000)
NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
PERCPU: Embedded 11 pages at c1606000, static data 24444 bytes
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 194911
Kernel command line: root=/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b ro console=ttyS0,115200
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
NR_IRQS:512
PID hash table entries: 4096 (order: 12, 16384 bytes)
Fast TSC calibration using PIT
Detected 1326.894 MHz processor.
Console: colour dummy device 80x25
console [ttyS0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Initializing HighMem for node 0 (00000000:00000000)
Memory: 772708k/786240k available (2905k kernel code, 12976k reserved, 1052k data, 392k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xfff4e000 - 0xfffff000 ( 708 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf07d0000 - 0xff7fe000 ( 240 MB)
lowmem : 0xc0000000 - 0xeffd0000 ( 767 MB)
.init : 0xc04e3000 - 0xc0545000 ( 392 kB)
.data : 0xc03d647f - 0xc04dd6a8 (1052 kB)
.text : 0xc0100000 - 0xc03d647f (2905 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop (skipped), value calculated using timer frequency.. 2654.36 BogoMIPS (lpj=4422980)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 64K (32 bytes/line)
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 10k freed
ACPI: Core revision 20090320
ACPI: setting ELCR to 0200 (from 8c20)
weird, boot CPU (#0) not listed by the BIOS.
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
SMP disabled
Brought up 1 CPUs
Total of 1 processors activated (2654.36 BogoMIPS).
net_namespace: 1056 bytes
Booting paravirtualized kernel on bare hardware
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using PIC for interrupt routing
ACPI: Power Resource [URP1] (off)
ACPI: Power Resource [URP2] (off)
ACPI: Power Resource [FDDP] (off)
ACPI: Power Resource [LPTP] (off)
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
pci 0000:00:07.0: PME# disabled
pci 0000:00:10.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:10.0: PME# disabled
pci 0000:00:10.1: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:10.1: PME# disabled
pci 0000:00:10.2: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:10.2: PME# disabled
HPET not enabled in BIOS. You might try hpet=force boot option
pci 0000:00:11.0: quirk: region 0800-087f claimed by vt8235 PM
pci 0000:00:11.0: quirk: region 0400-040f claimed by vt8235 SMB
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 12 14 *15)
PCI: Using ACPI for IRQ routing
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 10 devices
ACPI: ACPI bus type pnp unregistered
system 00:05: ioport range 0xe900-0xe90f has been reserved
system 00:05: ioport range 0xea00-0xea0f has been reserved
system 00:05: ioport range 0xeb00-0xeb2f has been reserved
system 00:05: ioport range 0xec00-0xec7f has been reserved
system 00:05: ioport range 0xe800-0xe83f has been reserved
system 00:07: ioport range 0x3e0-0x3e7 has been reserved
system 00:07: ioport range 0x4d0-0x4d1 has been reserved
system 00:07: ioport range 0x800-0x87f has been reserved
system 00:07: ioport range 0x400-0x41f could not be reserved
system 00:09: iomem range 0x0-0x9ffff could not be reserved
system 00:09: iomem range 0xe0000-0xfffff could not be reserved
system 00:09: iomem range 0x100000-0x2fffffff could not be reserved
pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
pci 0000:00:01.0: IO window: disabled
pci 0000:00:01.0: MEM window: 0xddd00000-0xdfdfffff
pci 0000:00:01.0: PREFETCH window: 0x000000d5c00000-0x000000ddbfffff
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Unpacking initramfs...
Freeing initrd memory: 633k freed
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1248948860.509:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 1510
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:00:01.0: disabling DAC on VIA PCI bridge
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
Using IPI No-Shortcut mode
registered taskstats version 1
Initalizing network drop monitor service
Freeing unused kernel memory: 392k freed
:: Loading Initramfs
:: Running Hook [udev]
:: Loading udev...SCSI subsystem initialized
pata_acpi 0000:00:11.1: can't derive routing for PCI INT A
pata_acpi 0000:00:11.1: can't derive routing for PCI INT A
done.
Waiting 10 seconds for device /dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b ...
Root device '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b' doesn't exist, attempting to create it
ERROR: Failed to parse block device ids for '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b'
ERROR: Unable to detect or create root device '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b'
You are being dropped to a recovery shell
Type 'reboot' to reboot
Type 'exit' to try and continue booting
NOTE: klibc contains no 'ls' binary, use 'echo *' instead
If the device '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b' gets created while you are here,
try adding 'rootdelay=10' or higher to the kernel command-line
ramfs$
I think what is happening is that the kernel does not have the drivers for the IDE controller on the board for the CLE266/VT8235. Does this seem accurrate? And if so, how can I verify the current kernel config, then compile a kernel with everything else Arch needs to boot properly? I am familiar with the old means of setting up a kernel using the 'make menuconfig; make; make modules_install' etc method.
Thanks for the help in advance!

Hi, not sure if this is still causing you an issue, but I just ran into the same problem.
For me, I have a Sharp PC=MM1110 which has no cd drive and doesn't like to boot from USB. To get Arch installed on it, I had to attach it to another PC (via it's docking cradle, which lets it show up as a USB hard drive), then boot the other PC from an Arch install cd and select the USB hdd for all of the partitioning etc.
When I rebooted after the installation, the Sharp wouldn't boot.
First, I had to edit the grub menu entry to point to (hd0,0), at which point I got the error listed in the first post... Failed to parse block device id's.
If i booted into fallback mode, it booted without a problem.
For me, the solution to finally get it working was to boot into fallback mode, remount the filesystem as r/w, and run mkinitcpio -g filename to rebuild the kernel. Once completed all I had to do was point grub to the new kernel image and it booted ok.
Hope this is useful to someone

Moving a drive from a NAS200 Question

Im thinking of moving from a NAS200 to one of the newer models with Gigabit. Can I move the drives from the NAS200 to the newer models without having to reformat?
Jorge
Solved!
Go to Solution.

Hi Jorge,
Moving a drive from NAS200 to NMH will reformat the drive because they are using a different file system. You should back-up your data first before moving the drive. Check out this linksys article: KB17899 - Swapping Hard Disk Drives between NAS200 and NMH Series Media Hub.
Hope this helps.
If everyone needs to believe in something, I believe I'll have another beer..

Moving XP drive to a new Mac Pro

I have an install of XP via Boot Camp on an old Mac Pro. It exists on it's own hard drive installed in the machine.
I'd like to move it to a new Mac Pro.
Is it as simple as moving the drive to the new machine?
When I run boot camp on the new machine will it recognize the previous install? Or will I need to do a new install?
Thanks
Dj

It 'should' work, but XP will see it is on different hardware and require activation or something. And, you always need to boot from XP CD once when moving it to do some system repair from what I heard.
If you want to address 4-8GB RAM; use both cpus, have better multi-core support, I wouldn't even use XP.
So depends on if this is retail or system builder whether you can deactivate and move the license.

Moving a drive with OSX to another computer? take it out of my Mac pro laptop and into my mac mini. can with be done with no OS/Hardware issues?

moving a drive with OSX to another computer? take it out of my Mac pro laptop and into my mac mini. can with be done with no OS/Hardware issues?

babowa wrote:
Thanks; however, I was really referring to this: if it is preinstalled on a Mac, I believe the license is for that computer only (unlike an MAS purchased version which can be used on any Mac owned). Has that requirement changed?
At this moment, that's correct. The OS X license included with a Mac can only be used with that Mac. However, in the case the OP has purchased OS X Mountain Lion in the past, this may change

Moving a drive with OSX to another computer? take it out of my Mac pro laptop and into my mac mini. can it be done with no OS/Hardware issues?

moving a drive with OSX to another computer? take it out of my Mac pro laptop and into my mac mini. can it be done with no OS/Hardware issues?

When I work with a drive to boot many computers, I use the newest model computer I will be booting, and set the system up on that, run all the Apple updates. Normally I will have no issue booting any older computer with the same drive. Unless of course those older computers do not support the operating system on that drive.
If you want to test if the drive will boot the mac mini. Put your MacBook Pro into target mode. Connect the two computers together. And on the Mac Mini, go into system preferences and then under start up disk and see if the target disk mode computer's drive shows up there. Seelct that drive and restart. See if it boots ok. A bit easier then taking the drives out and moving things around.

Moving TM Drive to New Mac

I've been backing up from my MacBook Pro to a wired drive for a while. I've just got myself a Mac Mini and plugged the drive in there instead. I'm trying to carry on using the same Time Machine backup for the MBP wirelessly, with mixed success so far.
I've shared the drive and pointed the MBP to its new place, and it's accepted it, although I haven't allowed it to start a backup yet as I wanted to make sure I could access the old ones first. When I enter Time Machine it says the current backup can't be found and gives me the option to select either the "old" one for the MBP, or the new mini's backup. So I'm sort of half way there, but I'm worried about this step of having to point it to the old one because the "current one can't be found." I'm wondering if this means it will insist on starting a new backup for the MBP from scratch, which will take a long time over wireless, not to mention taking up several dozen gigabytes somewhat unnecessarily.
Any advice will be appreciated

I got started with a solution from your article, perhaps someone can help me get over the next hurdle!
By starting a new backup over the network and cancelling it after "preparing," I got my blank sparsebundle, and decided to try moving my old backups to the sparsebundle ... simple idea in theory, but I'm getting help up by an "error code -50". I've seen solutions to this error when you want to copy it from one HD to another HD, but nothing for copying from a folder to a sparsebundle disk image. Can I get any help getting over it?
The other problem is I've found that if I decide to start a new one from scratch (which is a giant pain), plugging back in via USB to finish the first backup in good time won't work because it'll default to the old backup on in the Backups folder rather than the sparsebundle. I don't under any circumstances want to delete the old backup, it still needs to be accessible.
So I seem a bit stuck whatever I do... any help is as appreciated as ever

Moving boot drive - will mac recognize ?????

I'm going to add 2 200gb internal ultra ATA/100 drives to my G4 dual 1ghz MDD. There are only room for 2 ATA/100 drives(rear bay) , and my boot is taking up one of the slots. I was thinking of moving my boot drive to the front bay(ata/66, and installing the 2 new drives to the rear bay. My question is.......... will the mac automatically recognize where I've placed the boot drive??? Or will I need to boot from my install disc to pick the new boot drive??? Also, can someone verify that MDD g4's are set up for large drive support???? thanks

"will the mac automatically recognize where I've placed the boot drive???"
Yes. Physical location of the drive does not matter.

Folders moved from Drive C to Drive D... Need help!

Dear All,
Recently I had moved my iPhone Ringtone and Music original folders from drive C to drive D. Apparently, when i tried to sync my iPhone with iTune, it says,
"Are you sure you want to sync music? All existing songs and playlists on the iPhone "iphone name" will be replaced with songs and playlists from your iTunes library."
But when checked, even the iPhone Apps folder in my laptop is also empty, because it says the same thing.
So can someone please advise me on this?
Thank you very much in advance.

Dear All,
Recently I had moved my iPhone Ringtone and Music original folders from drive C to drive D. Apparently, when i tried to sync my iPhone with iTune, it says,
"Are you sure you want to sync music? All existing songs and playlists on the iPhone "iphone name" will be replaced with songs and playlists from your iTunes library."
But when checked, even the iPhone Apps folder in my laptop is also empty, because it says the same thing.
So can someone please advise me on this?
Thank you very much in advance.

MOVED: 「Display driver has stopped working and recovered successfully」

This topic has been moved to GAMING Notebooks.
https://forum-en.msi.com/index.php?topic=250960.0

Does this happen when you run the game by using dGPU(NVIDIA graphics) or iGPU(Intel graphics)?
(Check the color of your power button light, it lights red when dGPU is running and blue when iGPU is running)
Does this happen on all games you play or just one single game?
Tell your current graphics driver version(both NVIDIA and Intel graphics driver).
If you're running the game with NVIDIA graphics, check your vbios version in NVIDIA control panel(Right click on the desktop> NVIDIA Control Panel> System Information>Video BIOS). There is version 80.04.EF.00.22 released on the MSI website, and if you have a different one, I'd suggested to update the VBIOS and see if the problem still remains.
VBIOS Download link: http://dl.msi.com/download_files/frm_exe/N15P-GX-B_80.04.EF.00.22.zip
VBIOS Update Guide: http://www.msi.com/files/pdf/VBIOS_Update_under_DOS_mode_EN.pdf

MOVED: Display driver stopped responding and has recovered. MSI GTX 670 Power Edition

This topic has been moved to Graphics Cards.
https://forum-en.msi.com/index.php?topic=251843.0

Hey there,
Noticed that my BIOS drivers were outdated so i updated them (Z68A-GD65 G3, version: 25.8), after all the reboots i logged on my computer, started teamspeak, and while searching for the teamspeak room the driver problem happened again.
Anyway, my power supply is NOX Hummer 80 600W, model: HUM80600.
The problems started on September of this year i think? I've had this computer for almost 3 years now. I have the latest Nvidia drivers, and this still happens, i've tried downgrading, fresh installing, and nothing worked.
Graphics card: MSI GTX 670 Power Edition 2GB GDDR5 PCI-E 3.0 DirectX11, S/N: 602-V284-02SB1207063830.
I'll try it tommorow if possible.
Thank you for the attention.

MOVED: Need driver for MSI PC60G-F wireless card.

This topic has been moved to Other MSI products.
https://forum-en.msi.com/index.php?topic=145803.0

Quote from: novicagolubovic94 on 15-February-11, 03:00:50
Okay, so I open devce manager i select mu wireless card, right click, update driver and it opens "hardware update wizard" can windows connect...? - no, next
then I click on "install from a list of specific location" next
then "search the best driver in this location" then "include this location in the search: C:\Documents and Settings\Malossi\My Documents\Downloads\_PC60G-F_2000XP" next,
And it saids "Cannot continue the hardware update wizard" :S
do not choose "search for best",
choose "Don't search. I will choose the driver to install"

MOVED: Vista Driver for P4M890M coming out at all?

This topic has been moved to Intel Core Duo and Core 2 Duo based boards.
https://forum-en.msi.com/index.php?topic=106248.0

Nope, only for S3/VIA's Chrome9 based integrated graphics that support DX9 in hardware (e.g. K8M890, P4M900, CN/VN/896, and forth-coming Northbridges). VIA will only support older IGP through XPDM drivers.
Try the latest drivers for XP/2000 (if you haven't already):
http://www.viaarena.com/Driver/P4M890_16945205_XP_wIShld_logod.zip
Uninstall the current drivers first, if available through Add/Remove Programs. You may need to skip the install program and just manually install the driver by pointing New Hardware Wizard to the installation and driver files.

Moving system drive to another machine

Hi there,
I just got a new machine that currently has a bootable system drive. I have moved my old bootable system drive to this new machine as well. When I start the machine the new bootable system drive is the drive that provides the operating system. I would like to make the new drive not bootable so the bootable system drive from my previous machine is the system drive. How can I do that?
Cheers

Note that this is probably not possible. Although there are a few exceptions to the rule, in general, you cannot boot from a system that is older than the one that shipped with your machine. If your machine had 10.6.7 installed, it can't boot from anything before that, even 10.6.6. See:
http://support.apple.com/kb/HT2186
So, you probably can't boot from your old drive on the new machine. You'll have to either update the OS on that drive or migrate the data to your new machine's drive.

MOVED: MSI driver kills my operative system

This topic has been moved to Intel Core-iX boards.
https://forum-en.msi.com/index.php?topic=168889.0

Quote
If I choose to install "Intel 7 Series Chipset Driver" and open up the readme file that comes while downloading this driver. Inside the readme file it says version 9.3.0.1021 on july 4 2012. But according to MSI homesite it's drivers from 2013-01-18. So why is there two different date on this release? I notice that all the current drivers on the msi site has different release dates on their homesite compared with each driver readme file.
That's pretty irrelevant. The driver works. Just try it.
Quote
Also another issue with my modeboard, GHZ is not showed in the task manager. Please check link below.
dropbox.com/s/b7g9ffm8us19svi/problem.gif
No real problem but Win8 issue. Check with CPU-Z

MOVED: Network Driver Problem

This topic has been moved to Intel Core-iX boards.
https://forum-en.msi.com/index.php?topic=163944.0

OK:
Let's try this...
Download and run this driver again.
http://h20565.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=6559745&swItemId=vc_140782_1&swEnvOid=405...
Now, go to the device manager and click on the ethernet controller needing drivers.
Click on the driver tab. Click on update driver. Select the Browse my computer for driver software option and then at the bottom of that window, select the Let me pick from a list of device drivers on my computer.
Then click on Have Disk and browse to: C:\SWSetup\sp69909\WIN7\64\hp64win7, and select the Realtek PCIe GBE Family Controller from the list of ethernet controllers and see if the driver installs that way.

Moving TM drive

Similar Messages

Maybe you are looking for