Windows XP x64 RC1 on a RAID-0 array?

Hey all. This is the wrong forum for this post, so technically I'm breaking a rule. But then, there's no right forum for ATI Radeon Xpress motherboard issues, and technically my problem isn't even with that.
I have an MSI RS480M2-IL motherboard, which comes with the SiI 3112A SATA chip. Now I'm trying to install Windows XP 64-bit edition on a striped array done with that chip.
So the first problem was the diskette given by MSI. It's only a 32-bit driver disk. I found out that SiliconImage will hand out drivers for the 3x12 series under the heading of their latest product, the SiI 3512. (Follow this link to see the relevant drivers.) So I managed to get 64-bit drivers that presumably work with the SiI 3112A.
Now when I get through the Windows XP 64 bit RC1 cd, it ends on the note of "Unmountable boot volume" when confronted with the issue.
There may be many things that conspire against me on this. For example, the SATA/RAID controller initializes twice. The first time, if I try to enter its menu, it says that the computer doesn't have any drives. The second time, if I try to enter its menu, it goes fine and shows me my striped array.
Or maybe Western Digital and Page Computers sold me a faulty drive.
Or maybe the driver, which is over a year old, doesn't sufficiently handle the 64-bit architecture of the latest Windows Release Candidate.
Any advice?
Any better forum to put this in?

The driver probably pre-dates RC1 build 1289 and does not have the required NTamd64 labels. It will no doubt work for build 1218.
Follow the link on the CD (burned from ISO) to the release notes and you will find instructions on editing the inf file to add the labels. Actually those instructions are not very accurate because they say edit the manufacturer and models sections but some have found (e.g. with nvidia drivers) that you need to leave the existing sections intact and add new sections with the NTamd64 suffix.
You need to do this to the inf file that goes on the F6 floppy. Plus you need to do it to any other drivers or once you've got Windows loaded you can instead edit the registry to delete the inf file verification.

Similar Messages

I cannot install windows 7 x64 with AMD/ASUS RAID driver

Trying to install Windows 7 Ultimate x64 on an ASUS M5A97 mobo with AMD SB850 RAID, two WD 750GB drives configured as RAID 0. No drives are recognized by W7 install, so I choose Load Drivers. I put the drivers on a USB stick. Install finds the drivers there,
starts loading them, then comes back with "Installing an unsigned 64 bit driver is not supported and may result in an unstable Windows installation." I downloaded the latest drivers from ASUS website which are WHQL certified (as are the one's on the motherboard
disk). I saw other posts that recommend clicking Repair instead of Install, but I don't see where that option is. All I am given as options are Upgrade or Install. Choosing Upgrade tells me to boot Windows first. But this is a brand new install so...
I tried pressing F8 as setup was booting and chose "Disable Signed Driver Requirement" but that had no effect at all. If I turn off the RAID W7 sees both disks and happily installs. I see related posts going back to 2009; surely someone has
a solution for this issue?
Da Bomb

Hi guys,
I have been struggling with the same issue.
Win7 x64. Gigabyte GA-X79-UD3 Mobo with Intel core i7-3930K at 3.20 GHz
Marvell 88SE9172 SATA RAID controller with two Hitachi 500 GB spinning disks configured as RAID1
Windows would get to the point of asking for a mass storage drive. It would not see the RAID I had created.
Tried every driver I could find. Tried drivers from the "Station Drivers" website. Tried Marvell drivers for the same chip from the ASUS website. No luck. Tried loading from CD as well as USB flash drive. Always the same result... Windows would find
the drivers appropriate for the hardware found, I would select the RAID version, and after a few seconds, would report that the drivers were unsigned, and the installation was not supported for 64-bit drivers. Clicking OK would take me back to the load drivers
display with no new drives listed in the available drives window.
I tried hitting F8 during startup, and selected the "allow install of unsigned drivers option". That didn't do ANYTHING. Still the same error.
Someone suggested putting the drivers in the root directory. That didn't work. I also disabled all other drives except one CD rom and a USB drive and made sure that my RAID array was the first drive in the boot list.
Tried doing a windows repair, as someone else suggested. (This is an option that is available on the install disk I am using. It's enabled as part of EMS (emergency management services) in setup. Anyway, this was reported to be a workaround
to the signed driver issue. It would allow me to browse to the individual files, but no matter which one I selected, the response was "cannot find hardware appropriate to the driver selected" or some such nonesense. So I gave up on that.
Doing the install with the controller in IDE mode with just one drive connected, would result is Windows installing without a hitch. The problem was clearly when I presented 64-bit windows with a controller in RAID mode.
Long story less long, here's what worked for me....
Out of desperation, I began trying other subfolders in the driver lists. The Gigabyte manual indicated that the AMD64 subfolder was the correct one for the Marvell controller, when using RAID mode with 64-bit Windows. After trying every subfolder of
every driver I could find, the driver in the i386 folder actually worked. It initially came back with the same error about unsigned drivers, but after clicking OK, my RAID drive showed up in the list. I have been able to partition and format
the drive from within Windows setup, and am continuing with the install now. Hopefully won't be any problems booting from the drive post install, but so far it looks good, and I'm relieved that I was able to get it this far.
The whole process has been one of the most frustrating computing experiences I've ever had. This is what it was like back in the 90's when building PCs from scratch. I'm amazed that in this day and age the process is still so poorly documented
and filled with potholes, traps and caveats. Shame on the entire PC industry for allowing this to continue. I'm not asking that they jump in and try to automate it and do all the thinking for me (their solution for everything lately)...all I'm asking for it
clear, concise and accurate INFORMATION.
With the right information, and software that provides accurate feedback, this would all be easy...and even fun.
Hope this helps someone faced with the same problem.

CHKDSK fails on fresh install of Windows 7 x64 on mid-2009 MBP with SSD

There was an earlier post about this that has been archived prematurely that I will reproduce below. The main issue is a flaw in the Windows 7 x64 CHKDSK of the SSD drive in the mid-2009 MBP= 5,2. With fresh OSX installs, bootcamp 3.1, Windows 7 x64 all updates, the CHKDSK operation checks files at about 1 per second in stage 4 of 5, verifying file data.
Moderators: please leave this open until it is actually resolved.
Earlier posts:
Panajev
Posts: 4
From: ITALY
Registered: Oct 14, 2009
Windows 7 x64, MacBook Pro, frequent CHKDSK after HDD firmware update
Posted: Nov 2, 2009 6:45 AM
Hello, I have been having filesystem problems on my Windows 7 partition since the HDD related firmware update (the latest Performance update) was released and installed onto this mid 2009 MacBook Pro.
The HDD is a 500 GB 7200 RPM model, but it never gave me any troubles under OS X before the "fix" and I know other users had intermittent problems with the HDD on their MacBook Pro's related to the HDD making noises and pausing.
The fix was released, I installed it and I started seeing my first problem in Windows 7 x64 a few days after... I cleanly shut the OS down, but when I booted it back it asked me to perform a coherency check to the Filesystem... I thought that the problem was related to the fact that I was using the RC1 build of Windows 7... although that problem never manifested itself in the weeks before the Performance Update (HDD firmware fix) was installed and Windows 7 x64 RC1 had been on there and used frequently.
I recently purchased Windows 7 retail a few days ago and after a bit of trouble-free operation I started having problems again... always shutting the PC down carefully and I was asked to run the CHKDSK utility at boot twice already.
What to do?
Message was edited by: Panajev
MacBook Pro (2009) Mac OS X (10.6.1) Windows 7 x64, Bootcamp 3.0, recent HDD update
nicegom
Posts: 6
Registered: Nov 12, 2009
Re: Windows 7 x64, MacBook Pro, frequent CHKDSK after HDD firmware update
Posted: Nov 12, 2009 1:40 AM in response to: Panajev
Hi there,
I have a different experience. I installed Windows 7 before the "performance update 1.0" came out. I actually experienced the chkdsk launch problem with Windows 7. I had done repartitioning and clean-install several times but cannot solve the problem. So I tried to install XP and Vista on my MBA (Mid 2009 with SSD) and found that these two OS doesn't introduce such problem.
To be honest, I'm not sure which caused such problem, Windows 7, a bootcamp driver, or EFI. But I'm sure that CHKDSK in Windows 7 has an obvious bug that needs to be patched (memory leak and maybe this problem as well). So now I'm using Windows Vista SP2. And I'm happy with Vista SP2 (seems to become faster and stable now).
Cheer,
Message was edited by: nicegom
Macbook Air Windows Vista MBA of Mid 2009 with SSD

Windows 7 x64 all updates
Just doublechecking. Does that include the recent chkdsk hotfixes?
[The Chkdsk.exe program does not start correctly on a Windows 7-based computer|http://support.microsoft.com/kb/975778]

Windows 7 x64, MacBook Pro, frequent CHKDSK after HDD firmware update

Hello, I have been having filesystem problems on my Windows 7 partition since the HDD related firmware update (the latest Performance update) was released and installed onto this mid 2009 MacBook Pro.
The HDD is a 500 GB 7200 RPM model, but it never gave me any troubles under OS X before the "fix" and I know other users had intermittent problems with the HDD on their MacBook Pro's related to the HDD making noises and pausing.
The fix was released, I installed it and I started seeing my first problem in Windows 7 x64 a few days after... I cleanly shut the OS down, but when I booted it back it asked me to perform a coherency check to the Filesystem... I thought that the problem was related to the fact that I was using the RC1 build of Windows 7... although that problem never manifested itself in the weeks before the Performance Update (HDD firmware fix) was installed and Windows 7 x64 RC1 had been on there and used frequently.
I recently purchased Windows 7 retail a few days ago and after a bit of trouble-free operation I started having problems again... always shutting the PC down carefully and I was asked to run the CHKDSK utility at boot twice already.
What to do?
Message was edited by: Panajev

Hi there,
I have a different experience. I installed Windows 7 before the "performance update 1.0" came out. I actually experienced the chkdsk launch problem with Windows 7. I had done repartitioning and clean-install several times but cannot solve the problem. So I tried to install XP and Vista on my MBA (Mid 2009 with SSD) and found that these two OS doesn't introduce such problem.
To be honest, I'm not sure which caused such problem, Windows 7, a bootcamp driver, or EFI. But I'm sure that CHKDSK in Windows 7 has an obvious bug that needs to be patched (memory leak and maybe this problem as well). So now I'm using Windows Vista SP2. And I'm happy with Vista SP2 (seems to become faster and stable now).
Cheer,
Message was edited by: nicegom

Reinstall of Windows 7 x64 on WD 750 HDD and set up of m-SATA Caching

I am sorry but non of the above have any answers to my question.
A Tech from my OEM ran Disk Part in 12/13 thinking that it was a bad image. Unfortunately now no one can fix the Window 7 x64 install as MBR disk using the UEFI Bios.
I have called Microsoft Answer Desk have a Prem account. And most of the time I am told that the only way to run the install is to use the system in AHCI.
This of course take out the Intel RST and I can not configure the m-SATA and use 64GB as a cashing device.
When I call Intel the gave me a case number but after two days they said that after before I run the OS install to change the BIOS from AHCI to Raid.  Reset the drives from Control I then run the install from the OEM USB.
This is the guide they asked me to use:
1.Set the BIOS from with SATA mode to RAID
2. Install the Windows 7x64 from either the USB which as all Alien software or the Windows DVD
3. If installing from the DVD once Windows Installer comes up go to F6 and install the INf files for the Controller for the in order to load the drive Partitions.
4. Delete all the Partitions and run the Windows Install
    Having the USB to install from I don't need to do the above process.
What no one is telling either from the OEM, Intel, or Microsoft is when I am in the BIO's where do I run the install from. Is it the Legacy cd/dvd or the Legacy USB.
Or do I use the UEFI DVD which clearly spells out the name and type of dvd,blue Ray drive I have.
Or do I use the UEFI USB which again spells out the type of drive it is.
Every time I use the UEF I DVD or UEFI USB the system will install the disks as GPT and this is a major mess.
There is one more option no one is explaining and that is if I install using the Legacy DVD or USB the is another line in the booting section of the BOIS that sets the system as a boot UEFI BIOS.  This can be changed
to a legacy bios and I can still keep the OROM which is the Control I needed for Caching the m-sata.
CAN YOU PLEASE HELP. PLEASE SEND ME AN EMAIL AS TO WHICH PART I HAVE RIGHT AND WHICH PART I NEED TO CHANGE. IF EVERYTHING IS WRONG PLEASE SEND ME INSTUCTIONS AS TO THE CORRECT PROCESS.
I HAVE BEEN WORKING ON THIS SYSTEM FOR SO LONG NIGHT AND DAY. READ EVERYTHING I CAN FIND ON THIS FROM TECHNET TO INTEL AND SERVERAL TECH FORMS NO HAS THE ANSWER AND I HAVE A $3500 UNUSABLE SYSTEM
Thank you so much for letting my post.
[email protected]
Next go to the Control panel and run from the
The following is my system configuration:
Alienware 17
OS Windows 7 Ultimate x64
Bios is a UEFI Bios that can be set to legacy or UEFI
CPU: Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz Intel Haswell Revision 0/6
Intel Chipset version 9.4.2.1017,
Target PDH/Chipset xeon Processor E3-1200 v3 and v4 Intel 8 Series, C220
Intel Lynx Point HM87 v9.4.0.1017
Intel Rapid Storage: ver. 12.9.0.1001
Intel HD Graphics 4600 ver. 15.33.14.64.34.12
NVidia GeForce GTX 780M
Memory: DDR3 1600 MHz SODIMM - size each = 4GB x 4 = 16GB
Ethernet: QUALCOMM Killer e2201 Gigabit NDIS 6.20
Wi-Fi: Broadcom 802.11ac BCM 4352 BT 4.0
Storage Device For OS: WDC WD7500BPKX-75HPJT0 750.1 GB 7200 RPM SATA-600
Storage Device For Accelerated Cache: LITEONIT DMT-80M6M-11 mSATA 80GB SATA-600 TRIM Disabled
DVD Writer: LG Electronics HL-DT-ST DVDRWBD CA40N SCSI CdRom Blu-ray Read Only
System Must Have Supported Software: AlienwareRespawn Ver. 15 for Windows 7
Alienware Autosy = not a much have but nice to keep take of hardware issues and warranty
Alienware Command Center Includes: /Adrenaline Performance Monitoring and /Game Mode Also includes Fusion for Quick and Advanced Power Plan Settings Controls AlienFX with controls
Keyboard color display which can be connected to System State. Events, and
Applications Alienware On Screen Display = Includes EMSC.dll for NT Kern Driver or Embedded System Control for Hardware Properties DSubOSD Supports Display In HDMI
Sincerely, Frances Steele

Due to the Disagreement between a few OEM techs some of them insist that I install as UEFI with GPT and yet other insist I use Legacy. So the problem starts with setting up the BIOs correctly.
When the system was received in Oct 2013 the Boot options began with Windows Fast Boot = Disabled
I had both options at that time of Legacy or UEFI
I must admit I don't remember if OROM was enable or disabled.
I have both options and I can find am unable to clearly define which options is best.
So I have made many phone calls to the OEM requesting help with this set up.
I am certain of at this point is that when they sent me a USB that was for
Windows 7 with out SP1 the system installs and the drives are formatted as MBR. The best part of this USB is that it had the correct Alienware software (AlienAutopy & Alien Respawn) both import
to this type of system.
I am also certain that when I use the USB that Alienware sent me with
Windows 7 SP1 it is clearly installing as GPT using UEFI install. I found and have a copy of the master install script that shows this action. So what I find is that when I use the USB with out any action from
me the system is automatically installed in the way. This USB doesn't have any of my drivers nor did it have Alien Autopy or Alien Respawn.
I got so tired of the back of forth misinformation I have been receiving, that I request that I pay for a 1 TB completely Imaged drive that match my system.
I received it on 4/02/14 along with a the World Wide Tech service came to install it.  My first question to this tech before he even touched the laptop was, do you understand that I had a m-SATA
installed and do you know how to set up the BIOs for this.
His answer was that this was not his job. So I asked him to please wait before he installed the drive and let me call Alienware to confirm that the BIOs was set correctly and what we needed to do in order for the Operating
System to be installed correctly.
His answer was that he didn't have time. I had to let him do his job and install the drive.
So I did.  Right after the install I new something was not right so I began copying every file I could find that contained drivers, Sysprep, all logs the complete System 32 Windows files and SysWOW Files.
After the first reboot I found that Alienware Respawn was not installed. So because I knew were to get it from I downloaded it. After trying to install the software I received and error message that stated that since it could not find a Windows Recovery
Enjoinment that it would not install.
I noticed that the system was formatted with the disks as MBR (I checked this under Device Manager and clicked on the HDD under Properties it showed that is was MBR)
There was a 38MB OEM partition - a 750MB Recovery Partition - and the rest of the drive was for the Operating System.
Because I made a copy of all the logs and files before the reboot I was able to go back and find the under Panther the original I found the Setupact file it is 908 KB and I wish I could sent you an attached copy of it because it has a lot of information
that would help in how the drive was installed.
Remember I told you that the Tech only allowed me to make sure that OROM was enable and that SATA was set to RAID so I was unable to set the boot to Legacy or UEFI. So from this file as you will see there are a number
of errors it would seem that that the drive was installed as UEFI. (Although everything I have read on the subject states that a UEFI install automatically formats a disk to GPT) So this is why I am so very confused.
Because I can not attach the file here and am going to copy and past some of the items that give me this impression:
2014-04-02 16:56:23, Info       [0x0601c1] IBS    InstallWindows:Install Path = C:\Windows\system32\oobe
2014-04-02 16:56:23, Info       [0x0601c2] IBS    InstallWindows:Setup Phase = 4
2014-04-02 16:56:23, Info                         [setup.exe] OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE]
--> [IMAGE_STATE_UNDEPLOYABLE]
2014-04-02 16:56:23, Info       [0x0601ee] IBS CreateSetupBlackboard:Successfully created/opened Setup black board path is [C:\Windows\Panther\SetupInfo]
2014-04-02 16:56:23, Info                  IBS    InstallWindows:No UI language from a previous boot was found on the blackboard. Using selected language [].
2014-04-02 16:56:23, Info                  IBS    InstallWindows:Setup architecture is [x64]
2014-04-02 16:56:23, Info       [0x0601d5] IBS    InstallWindows:Starting with Empty Queue. Setup Phase = 4 callBack_DiagnosticDataGeneration: Setup was started from Phase 4. Disabling Diagnostics [DiagnosticDataGeneration]
in this scenario
2014-04-02 16:56:23, Info       [0x060258] IBS    GenerateName: Failed to read the Key UserData\FullName\Value from Blackboard defaulting to WIN
2014-04-02 16:56:23, Info       [0x060259] IBS
GenerateName: Failed to read the Key UserData\OrgName\Value from Blackboard
2014-04-02 16:56:23, Info       [0x06025d] IBS
list of function drivers from the critical device database (CDDB).
2014-04-02 16:56:24, Info                  SYSPRP Waiting for thread to exit...
2014-04-02 16:56:24, Info                  SYSPRP Status: Total = 0, Complete = 0, Progress = 0% (0%)
2014-04-02 16:56:24, Warning               SYSPRP Installation was supposedly active, but status key doesn't exist?
2014-04-02 16:56:24, Info                  SYSPRP SPPNP: The device setup class for device ROOT\LEGACY_STORVSC\0000 is 8ecc055d-047f-11d1-a537-0000f8753ed1.
2014-04-02 16:56:24, Info                  SYSPRP SPPNP: Skipping device ROOT\LEGACY_STORVSC\0000 because it belongs to the legacy class.
2014-04-02 16:56:24, Info                  SYSPRP SPPNP: {Retrieving drivers used by device ACPI\PNP0C32\3}
2014-04-02 16:56:24, Info                  SYSPRP SPPNP: No device setup class has been specified for device ACPI\PNP0C32\3. We will not attempt to retrieve the device's class
filter drivers.
2014-04-02 16:56:24, Info                  SYSPRP SPPNP: No function driver specified for device ACPI\PNP0C32\3.
2014-04-02 16:56:24, Info                  SYSPRP SPPNP: No device upper filter drivers are specified for device ACPI\PNP0C32\3
2014-04-02 16:56:24, Info                  SYSPRP SPPNP: No device lower filter drivers are specified for device ACPI\PNP0C32\3
2014-04-02 16:56:24, Info                  SYSPRP SPPNP: {Retrieving drivers used by device ROOT\LEGACY_NTFS\0000}
2014-04-02 16:56:24, Info                  SYSPRP SPPNP: The device setup class for device ROOT\LEGACY_NTFS\0000 is 8ecc055d-047f-11d1-a537-0000f8753ed1.
2014-04-02 16:56:24, Info                  SYSPRP SPPNP: Driver isapnp was retrieved from the CDDB.
2014-04-02 16:56:24, Info                  SYSPRP Re-checking active
Now of course there is so much in the file I have skipped around and just pointed out the parts where I am hoping you will see installing legacy drivers and software were being skipped.
I called Alienware back and requested a level 2 tech I explained the situation and received a new 1 TB imaged hard drive today.
As I explained to the tech on the phone who again was uncertain if the BIOs should be set to UEFI or Legacy. I told him that we should try installing the drive with both USB's another possibility is to use Acronis Universal Restore and reinstall
from the backup that I made of the 1TB drive that is currently in the System now.
My worry (which I am most certain is valid) this that if we just drop the new drive in the system which making sure which BIOs setup is the most appropriate another Windows 7 x64 SP1 Ultimate will be destroyed. Because there is not
way to change the system from GPT to MBR or legacy to UEFI without having to reinstall the OS.
I have to admit that after 7 reinstalls on my own for one system I am really getting pretty sick and tired of working on this laptop. If I had the money I would make the purchase of an Origin PC in a heart beat but that would be $3200 that would match
the specs of this system.
I couldn't see the Recovery Partition so I Installed Acronis True Image 2014 Prem, and Backed up the disk. With this installed I was able to open the 750MB what I found was 1 folder for System 32 that has a folder with the name Recover but I am unable
to access it. was empty, 1 folder with the name Windowsre, in this folder there are 2 files one boot.sid and one winre.wim
I am not sure what you can do with any of this information but honestly any help would be most appreciated. Before Thursday 04/10/14 when I requested the tech who I spoke to today to return my call. At that time I am suppose to test out 3 or 4 difference
ways to install this drive and see if I can not find out what I am supposed to have in place for the BIOs before he helps me install the new 1TB HD. (which is the easy part)>
Sincerely, Frances Steele

Windows 7 x64 Network Adapter Stops working on high load

My Network has been failing and it has been happening for about a month or so on Windows 7 x64. I dont think that the system configuration is the problem as it is happening on 2 seperate machines. One being a relatively beefed up "white" box, 4 gig OCZ ram, EVGA nForce 790I SLI Mobo, Q9600 Quad core processor, dual raid 1 - 150 Gig Raptors, 2 8800GTX SLI cards, Pure Power 800W PS. The second machine is an IBM Netbook S10. I use the Netbook as a media center connected to a Pioneer Elite 1050HD. One thing is I have a PS3 and have several 1TB Esata drives connected to an IOGear 3132 Esata 3.0Gb pciX card to my desktop.
My typical usages:
1. FTP from a private server
2. Streaming music via Winamp
3. Streaming video 720, 1080 from pc to PS3 via the PS3 Media Server
4. DLing demos or movies on the PS3
5. Network streaming a movie from the Esata drives to the bedroom or kids rooms
6. Streaming video from abc.com or southparkstudios.com from the Cox cable modem
7. RDC over VPN to work machines
Now I have noticed that when I am streaming HEAVILY, from any 2 of the above mentioned, my network connections will simply stop working with a yellow exclamation mark on the task bar network icon after a few moments, nothing in the event logs, no logs or ANYTHING at all. It will simply stop working no notifications or anything poof, gone. I have EVERY single patch, driver anything I can think of installed. Nothing works, the timing is completely random. FYI I have a NETGEAR ProSafe VPN Firewall FVX538 with a cable modem connection on WAN 1 and a cellular connection on WAN2, these have no impact I feel on the connections because the PC may go down or the Netbook will go down depending on which one has the most load. So this simply tells me that it it not a firewall router problem as I have tried using a cisco unmanaged 24 port 1GB switch and I get the same problems. From analyzing the systems and layout I am led to believe that it is either a network adapter driver OR a Windows 7 problem (collisions, unhandled exception?), this NEVER happened with XP or Vista. I have tried everything but a new network adapter, I have tried the secondary adapter card on the mobo, I have tried bridging the two, I have tried daisy chaining the switch and putting each machine on its own dedicated switch linked to each other with no change. When the network goes down it is only that box effected, all other machines still connect to each other fine, only the one with load shuts down and the only ones that shut down are Windows 7. These machines are all wired with commercial cat5e patch cables, they have all been swapped for new ones lately. All networking and PC equipment are on UPS so I doubt voltage variations. Windows Firewall is disabled I only use the hardware firewall, I do not use any antivirus.
I am completely out of options, can anyone recommend a new route?
In addition when I go to the command prompt and attempt to do an ipconfig /release. I get an error saying that the adapter is not in a usable state. Very irritating, this forces me to reboot, or right click disable/enable on the network adapter. The right click route takes almost a minute to complete.
Tried update driver in nvidia control panel, no luck. I have also turned off the networking power saver option in the adapter settings.

Hi,
Considering this issue occurs on 2 different machines, I also think this issue may be more hardware related. You may also try the following:
1.    If the computers are connecting to a router, please ensure the router’s firmware is up-to-date.
2.    Please run the following command in an elevated command prompt in Windows 7:
netsh interface tcp set global rss=disabled
netsh interface tcp set global autotuninglevel=disabled
netsh int ip set global taskoffload=disabled
3.    Disable SNP in Windows 7 by setting Registry as following:
Note: Please perform a full-system backup first.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
EnableTCPChimney=dword:00000000
EnableTCPA=dword:00000000
EnableRSS=dword:00000000
If the keys do not exist, please create them and assign the value.
An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers
4.    If the issue persists, please add another network adapter to this computer and see how it works.
Hope this helps. Thanks.
Nicholas Li - MSFT
Hi, I'm experiencing a simular problem here.
My PC was using Asus P5Q-E motherboard but exchanged it for Asus P5Q TURBO Pro because it loses 'connectivity ' after an interval between a few hrs to 26hrs. During this state, I can't browse or my Outlook to check emails. The only thing that can send/receive data is Vuze. Plus, the strange thing is that the network icon says there's nothing wrong at all (when it obviously there is). Even the currency desktop gadgets says the time elapsed since it 'lost connectivity '.
I initially thought P5Q-E was faulty so now I'm using the TURBO Pro. However, the problem still persisted.
I am using Win 7 Ultimate x64 with all the updates and drivers. Connected via LAN cable to the router and the firmware is the latest. My ISP sent me a replacement router to confirm that their equipment is not faulty, which is true.
I have tried the above methods 1-3.
Although I'm not sure if I implemented Method 3 correctly since I don't usually go to the registry but here's what it looks like after creating it:
EnableRSS   REG_DWORD   0x00000001 (1)
EnableTCPA REG_DWORD   0x00000001 (1)
EnableTCPChimey REG_DWORD   0x00000001 (1)
There are 3 more PC's and 1 laptop in the house. 2 PCs use Win XP, 1 uses Win 7 Ultimate x64 and laptop uses Linux Ubuntu.
My PC has a second OS, Linux Ubuntu, I used it to time trial both motherboards (before and after switching) and found no problems at all even after 48hrs, so it confirms it's not a hardware issue.
The other PC's apart from mine are connected wirelessly. As far as I've been told, they don't experience the same issue I have.
I've been trying to tackle this problem for months now and I'm frustrated to reboot my PC every time it 'loses connection '.
I chatted with Asus about the issue when I still had the P5Q-E mobo, they said that they built a simular system to mine with the same mobo and said they couldn't reproduce the problem I'm having. THey even tested on other mobos with the same LAN chip and found nothing wrong. That's why I got the TURBO Pro that has a different LAN chip.
Anyone got anymore suggestions???
Thanks in advance.

ITunes with Aiport Express on Windows 7 x64

Since I installed Windows 7 x64 RTM, I have had stuttering problems when connecting to an Airport Express to play music. When I only play the audio on my computer, it plays fine. When I connect to an Airport express (either by itself or with multiple connections) is when the problem occurs.
I have tried different network card drivers as well as another network card, and the problem persists. I did not have any issues with Vista SP2 x64.
System Configuration:
Windows 7 Home Premium RTM
Gigabyte AMD780G motherboard
AMD Phenom 9550 (quad core) CPU
8GB RAM
750GB HD (mirrored RAID)
AMD 4850 graphics card (1680x1050)
Onboard gigabit LAN / Linksys PCI gigabit ethernet card
iTunes 8.2.1.6
Airport Express firmware 6.3
All wired Gigabit connections (except the 100mbps wired Airport)
Any ideas?

So I uninstalled all iTunes related software (iTunes, Apple update, Bonjour, etc.), deleted all registry entries for anything Apple related, rebooted, and reinstalled. Same thing happens.
I changed the wireless channel on the airports (even though they are wired and setup as routers, with nothing connecting to either) the problem still persists.
As I mentioned previously, I had no problems with Vista x64. My other machine still has Vista 64 and has no issues. The problem is with the Windows 7 x64 (RTM) machine (which again, worked flawlessly with Vista x64 installed).
So, this is an iTunes not liking Win7 problem.

Windows 7 X64 & Premiere pro CS4 issues

Hi All,
I have a Dell Precision 690 with a clean install of Windows 7 X64 and a new (1st time) install of Production Suite CS3 (excluding Premeiere Pro CS3 and Encore CS3) and a new (1st time) install of Premiere Pro CS4 with Encore CS4.
After starting a new HD project (1920 x 1080 29.98) if I try to open any (old or new) sequence, the program does a "serious error" hicup and has to shut down.
Everytime I run Premiere Pro CS4 and try to load a project previously saved to the raid array that was created under XP Pro 32bit (previous life) I get this message saying that the scratch discs are write protected and would I like to change to the default (C drive) location for scratch discs. Within the original project the scartch disc was the external raid array. I can access that raid no problem from windows explorer and read and write to it. Also all the clips within the project are read from the raid so I don't get it. Anyone come across anything like this before?

try opening the project, clicking OK when it tells you that the scratches are write protected, and then when it opens, go to the top menu bar and click Project > project settings > Scratch discs and re-point your scratches to the location you want them. Save, and you should be good to go.

Windows 7 x64 can't read/install any printer drivers from Windows Server 2003 x64 (AMD64 folder and HP Deskjet 855c)

I read the thread Widows 7 printer
HP deskjet 855c driver about possible installation of HP855c drivers onto Windows 7 x64 from "Windows Server 2003 x64" CD but I didn't have enough luck to succeed with doing it on my laptop. That thread appears to be dead now
as it is marked "Answered", so I'm asking for help here. I have Toshiba Satellite P500 with Windows 7 Home Premium 64-bit (http://i55.tinypic.com/2zgth6v.jpg).
Let me tell you first that I don't have access to Windows Server 2003 x64 or XP Pro 64 CD's. However I did some research online, which eventually forced me to learn about the "file sharing". After extensive search I was able to get the copies
of AMD64 folders from Windows Server 2003 R2 Standard x64 with SP2 and
XP Pro 64. The reason that I went also after XP Pro was because I thought that the extra wording "R2 Standard x64 with SP2" in description of "Windows Server 2003" did not reflect the exact name provided by poster
Alan. I couldn't find just "Windows Server 2003 x64" (does it matter?).
Anyway, I followed first the drill with running "printui /s /t2" and disabling UAC, and then in both cases I was able to locate the
NTPRINT.INF file (http://oi51.tinypic.com/9qwvt2.jpg - this image is from XP Pro AMD64 folder) but each time when I
attempted to install the driver, I got the same message stating:
"The folder you specified doesn't contain a compatible software drive for your device. If the folder contains the driver, make sure it's designed to work with Windows for x64-based systems." (http://oi53.tinypic.com/27yveiw.jpg)
Why aren't there x64 drivers?
During several installation attempts I had the printer connected to or disconnected from my laptop. It didn't make any difference. I must add that for this purpose I had to use different cable than the original one designated only for the
Parallel port in my old desktop with Windows XP. My new laptop with Windows 7 x64 came only with 3 USB ports (plus 1 HDMI and 1 Serial). Because of that situation I bought in advance a new printer cable called “USB to 36-pin Parallel Port Adapter
Cable” (http://www.amazon.com/gp/product/B003A8I75E). I'm not sure, if it will work until I can install the printer.
Besides, nobody talked about this issue yet. I was also playing with the port choices in "Add printer" step; changing from default LPT1 to USB001 with the same negative results.
I don't know what I'm doing wrong. I was very hopeful after reading positive "case closed" notes there.
Can anyone help me here, maybe by making the necessary files available for download? I'm willing to pay for such assistance or make a donation, if necessary. Seriously. Judging by the large number of views of the original
thread, one could assume that there is a potential demand for such service. It would be more human to pay few bucks for a few driver files than $900 for the whole Windows Server 2003 x64 CD, no? Can Microsoft accomodate me/us, please? :)
Andrew*
P.S. I was advised to come for help here from
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/windows-7-x64-cant-readinstall-any-printer-drivers/4e7d06e1-33a5-4597-be70-4fdc087a63a7?msgId=9a045994-0d31-4d40-b17d-dba372393ee4

I have my HP 855c/driver working on Win 7 Ultimate x64. I used the 'printui /s' procedure and 4 files described above with some minor changes.
I pulled WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe down from the Microsoft website. Running the file causes the exe to unpack into a temp folder at the root drive. A 'Setup Error' message box is displayed once the file is run. I left this
message box up until I copied ntprint.inf, ntprint.cat, and sp2.cab from the temp folder.
I copied driver.cab from a Windows XP Pro disc. I also needed amd64\stdnames.gpd which was already in my Windows 7 c:\windows\system32\spool\drivers\x64\3 folder.
I created a folder with the 5 files (ntprint.inf, ntprint.cat, sp2.cab, driver.cab, and amd64\stdnames.gpd). This is my 'Have Disc' folder.
I followed the 'printui /s' instructions, first changing the permissions mentioned above and then installing the driver. Next I followed the instructions to add a printer from Control Panel 'Devices and Printers' - 'Add Printer', choosing to 'use an existing
driver' when installing the HP 855c.
I used a slightly different ntprint.inf, size 1570418. The readable contents of ntprint.inf is as follows. Notice the line 'CatalogFile=ntprint.cat' is not included. I tried using the 1570468 version of ntprint.inf; when I did I received an incompatibility
message (probably the same one mentioned above).
; NTPRINT.INF (for Windows Server 2003 family)
; List of supported printers, manufacturers
[Version]
Signature="$Windows NT$"
Provider=%MS%
; LayoutFile=layout.inf
ClassGUID={4D36E979-E325-11CE-BFC1-08002BE10318}
Class=Printer
DriverVer=10/01/2002,5.2.3790.4533
[ClassInstall32.NT]
AddReg=printer_class_addreg
[printer_class_addreg]
HKR,,,,%PrinterClassName%
HKR,,Icon,,"-4"
HKR,,Installer32,,"ntprint.dll,ClassInstall32"
HKR,,NoDisplayClass,,1
HKR,,EnumPropPages32,,"printui.dll,PrinterPropPageProvider"
Good luck

Windows 7 x64 on 2009 MB, step-by-step instructions and solutions

ok, after spending days on this with about 10+ clean installs on 2 different machines and searching forums about various problems, i'm going to go step by step in a flow-chart like manner to describe the steps and various pitfalls in getting windows 7 ultimate 64 bit installed correctly on a macbook (late 2009)...most of this i didn't figure out on my own, this is a compilation of solutions found by others. i'll try and link or credit anyone i can, but honestly can't remember where i saw all of this. part of this is to share my days of frustration to try and save someone some time. also, in case i have to do this again, i want a record of it so i don't have to start from scratch next time.
i don't have everything working perfectly, but i have wireless and sound, but not sure if all the drivers are up to date. i'm still working on the headphone issue, i don't have sound yet with headphones, but i got the speakers to work.
i'm going to preface this by saying that windows 7 is a horrible piece of software, i'm only helping a friend do it because she's an architect and needs autocad, but she wants a mac for daily use. also, i'm doing this from a spanish install of windows 7 (here in south america), so it's a pain to translate this cruddy convoluted OS into english as i'm not familiar with windows 7 anyway, so i'll do my best. i'm not a pc expert. also going to say that the windows 7 x86 and x64 installs i've done on a couple macbook pro 15's seems to work much better (full trackpad functionality, expose works) and without as many problems...i don't know why it doesn't seem to work as well in x64 on the macbook, i'm still investigating.
also, i want to say that a fresh (first-time) bootcamp partition with windows install after a clean mac os x install seems to produce the best results. i say this because i wasn't happy with all the hacks in my first couple attemtps, so i erased the bootcamp partitions and re-created them to re-install windows 7 again. but i started experiencing some peculiarities that never happened in the first install after a clean Mac OS X install. it's as if the computer leaves artifacts from previous installs and acts funny. also, reboots and start-up times seem to be slower now than when it was a first-time fresh install. anyway, i'll try and outline all the weirdness here, indicated by asterisks *
SO, HERE GOES:
1) Go to Bootcamp Utility > Create Bootcamp partition
2) Afterwards, this should take you to a restart into the windows install dvd....if install dvd boots fine, skip to step 3
** if you get a gray screen (happened to me after subsequent re-install attempts), you have to power off and reboot holding down "C" key to boot from the dvd...or you can hold down alt/opt key to get the icons of bootable volumes, at this point it should be mac os x and the windows dvd. the point is, force it to boot from the dvd if it hangs on re-start.
3) Windows install should start. Select language, etc....You should then get to a screen listing all the partitions (should be 3 of them). Choose the Bootcamp partition and format (erase) it to proceed with the install.
4) Windows should start installing all the files and will reboot a couple times, here's where things get weird possibly. On the first attempt at installing Windows 7, the install went smoothly on restart.
** some of you might get a blinking cursor and a black screen that goes on forever. Supposedly this is a bug in Windows 7, having to do with video drivers or something. I don't understand because my first install attempt, it rebooted just fine and the installation continued.
anyway, what you have to do here if you get the forever-black screen is power down the machine with the power button and restart holding the alt/option key. this time when you get the bootable volumes on the gray screen, choose the Windows partition, which will now appear. DON'T boot up from the DVD. upon restart into Windows, you should be back in the installation process and it will attempt to finish the install here.
it might be my imagination, but once i had to reboot into the dvd here to actually finish the install. technically Windows is not finished installing at this step, you just have to figure out how to get past the black screen to finish the install. try both.
5) Windows should go back to where it left off before the restart, then finish the install.....and restart AGAIN. On my first attempt, the restart went smoothly and started the "first time user" process...
** some of you will get the black screen YET AGAIN, this happened to me on my subsequent attempts at re-installing Windows. again, you need to power off and start up holding the alt/option key, choose the Windows partition and it should take you to the "first time user configuration" process....since at this point, windows is indeed installed.
6) Here you will fill out all your information, product key, etc...and get into Windows. Here you will have some other problems.
Problem #1: you have no drivers to run Windows on your Mac, so you will need to install Bootcamp in windows from your Mac OS X install dvd
Problem #2: you have no "right click", because you don't have drivers, so you might not be able to eject the Windows dvd to put in the Mac dvd
Solutions: you can't control-click or right click, BUT YOU CAN hover over the DVD drive ( "D:" in your computer, my PC or whatever it's called in english) and see if there's an "eject disc" option.
for some reason, my Windows dvd was spinning and not being recognized, so i just rebooted (alt/option) into Mac OS X and ejected the disc there. the point is, you need to eject the Windows disc and put in the Mac OS X install disc to access Bootcamp for Windows.
7) Reboot into Windows (if you had to boot into Mac to eject the disc). Insert Mac OS X install disc. Navigate to BootCamp setup.exe and run it.
** the first time i did this, it ran no problem. but in subsequent attempts, it gave me the "x64 not supported by this computer" message that everyone seems to encounter. there is a bypass for this outlined here:
http://www.techulous.com/hardware/how-to-apple-boot-camp-64-bit-for-windows-7-on -unsupported-macs.html
8) Ok, so now you should have Bootcamp 3.0 installed. Now you need to update it with Bootcamp 3.1 update. Download it here and run it. This is required for 64 bit support, I believe this is the link:
http://support.apple.com/kb/dl979
** hopefully you don't have problems, i didn't, so you might have to search the forums since i can't anticipate what might happen here, it worked for me every time.
9) Ok, i think it might reboot after the update install. Now you have Bootcamp installed and most of the drivers you need, however not everything works. Some of the drivers will be out of date.
Problem #1: you may or may not have updated nvidia drivers. mine are ok, but check nvidia website if you have doubts. most of their drivers are for PC hardware, however, so the ones on the bootcamp disk and update should be fine.
Problem #2: almost everyone has wi-fi connectivity problems. it has to do with the wrong/outdated broadcom drivers from bootcamp. i will outline how i got it to work (based on someone else's solution i found in some forum or other).
Problem #3: almost everyone is having sound issues. i'll explain what i did. i still have no sound coming out of the headphone jack, i'm working on that next. but i have speaker sound and no red light coming out of the headphone jack.
** first of all, you should probably download firefox from internet explorer in windows, then update adobe flash, it's a pain....i used another computer to download the drivers, then transfered them by USB drive, but you can do it however u want.
Solution to wi-fi: ok, not sure where i got this information, but i downloaded HP drivers in a file called "sp45524.exe"....here's the link:
http://www.wireless-driver.com/download/hp/hp-broadcom-wireless-lan-windows7-dri ver-v560188.htm
apparently the broadcom drivers in Bootcamp 3.0 and 3.1 update won't install on Windows 7 x64 for some reason, lot of people are getting "code 10".
what i did is this:
9a) run the .exe file, it will create a folder called SWSetup\SP45524 that will house the drivers. there's a setup file in that folder, i didn't try it. perhaps it will install from there, but everything i read suggested a different step. ** if you run the set up file, you may have to run as administrator, or use the "troubleshoot compatibility" trick to get it to work.
9b) Go to Control Panel > Hardware and Sound > Device Manager > Network adapters
you should uninstall or deactivate any drivers you have. if it's not showing any wi-fi adapter, right click and "check for new hardware" (not sure how it's translated into english from spanish)....you should have an unknown device pop up with the yellow icon and exclamation mark. double click on that, assign it as a network adapter.
when you get to the driver tabs, you can install it from there. this is where it gets tricky. click "install driver", "check drivers on this computer", "choose from a list of drivers on this computer", "use disc", and in the dialogue box ("install from disc" that says "copy manufacturers files from", navigate to the C: SWSetup|SP45524 folder and click until you can accept. this will load up a different list of drivers.
(sorry, i'm translating the Windows from spanish to english, and i'm not familiar with exactly what they say in english, so you'll just have to use your imagination)
you should now have a small list of drivers. personally, i chose the first one on the list "Wi-Fi adapter Broadcom 43224AG 802.11a/b/g/draft-n", but the second one worked also. again, i'm doing this on a late 2009 white macbook (6.1) and it works. according to the date of the driver, it seems like it might not even be the most current and might be older than the one that's on the MAC OS X install disc, but none of the ones on the disc work. this one does. (thanks to whoever found this out, i can't find the original link of the post with this driver reference).
Solutions to sound: ok, there are multiple posts on this, everything from updating realtek to sigmatel...personally what worked for me was to download the most current Cirrus Logic drivers.
everyone has been pointing to this post:
http://www.stuffedcow.net/macbook_audio
it doesn't really tell you what to do exactly. i'm not even sure what to do, but here's what i did. actually, i downloaded what was supposed to be the CS4207 driver here:
http://www.cirrus.com/en/products/pro/detail/P1233.html
then i followed the same procedure as before with the network adapter driver...."install driver", "check drivers on this computer", "choose from a list of drivers on this computer", "use disc", and in the dialogue box ("install from disc" that says "copy manufacturers files from", navigate to the folder you just downloaded from the above link.
you should have an updated list of drivers. what i don't understand is that the Cirrus site lists the most current driver as CS4207, but the only thing that has 4207 in it starts with CDB. in any case, i chose the last one on the list, CS4206A (AB 99).
i have no idea why i chose that, it just seemed to be the most current. in any case, sound works now.
Ok, i tested all this stuff in skype. wifi, microphone and speakers work, isight works. however, still no headphone sound. so if anyone knows how to fix that, please let me know. i haven't gotten to that part yet. but i've spent like over a week trying to figure this out. windows 7 is so horrible that there seems to be so many steps to getting it just right, and i just found myself starting all over (i didn't mention the nightmare with license breaks with AutoCad due to windows reading the clock differently...that's another hack that i had to deal with...and failure meant re-installing everything).
ok, off to bed now....

Windows 7 x64 all updates
Just doublechecking. Does that include the recent chkdsk hotfixes?
[The Chkdsk.exe program does not start correctly on a Windows 7-based computer|http://support.microsoft.com/kb/975778]

Windows XP X64 Soundmax ADI1986A Sound drivers

Windows XP X64 Soundmax ADI1986A Sound drivers
Does anyone have these drivers >>> Soundmax ADI1986A FOR WINDOWS XP X64
There is a X64 version working under Vista X64 Ultimate provided by the Lenovo site, but for XP X64 i found none.
I must say, with the UAA Driver for High Definition Audio 1986A X64 Windows 2003 installed, there is sound only in my headphones (so the jack is working) , but the speakers are off. I really do not understand how this comes.
Does anyone confronted with this issue ? Does anyone has a working XPx64 ADI1986A sounddriver ?
( I forgot to tell the notebook model lenovo 3000 N100 0768-bng intel core2duo T5500 )
Message Edited by adrian_butan on 01-04-2009 02:05 PM

I am in deep trouble finding those x64 drivers.
For the Bluetooth stack, it complains about being unable to find the Bluetooth device. It keeps on saying "Please plug in the Bluetooth device.". Nothing more...
For the sound card, Analog Devices does not provide drivers to individuals. Instead, they forward you to the OEM manufacturer web site, in our case the Toshiba downloads site, where you can find nothing.
I understand that Toshiba is not delivering those machines with 64 bit operating systems.

VS2005 Crystal Report Print Report Button is not working on Windows 7 x64

Hi There,
My application is written in VS2005 C# on x86 machine. It runs smoothly on XP pro and Vista x86 machine.
I deployed the same to windows 7 x64 machine with CRRedist2005_x64.msi and found that the Print Report button is not working.
So, I re-compiled my application to x64 target platform, and reinstall the application to the same machine. But nothing changed. I have surf for answer over the web but nothing found.
Please help urgently. Any helps is much appreciated. Thks in advance.
Edited by: chanpyvivian on Mar 26, 2010 11:14 AM

I follow your instruction as below:
1) download the sample app vbnet_win_printtoprinter.zip to dev computer and compile it to .NET 2005.
- Run from my dev computer
- Click "Print Report" button
- Error message display - please see below
    The error was due to the default printer name hard coded in the program was not found. I have edited to my printer name and it can be printed out with no error.
2) Use a "saved data" report so that you do not have to worry about database logon.
can't find the "saved data", please elaborate
3) Then copy the exe to the 64 bit box and try to print using this sample app.
-do you mean copy the exe to the 64 bit computer for testing ?
ERROR Message
CrystalDecisions.CrystalReports.Engine.InvalidArgumentException:
Invalid printer specified. ---> System.Runtime.InteropServices.COMException (0x80000201):
Invalid printer specified.
   at CrystalDecisions.ReportAppServer.Controllers.PrintOutputControllerClass.ModifyPrinterName(String newVal)
   at CrystalDecisions.CrystalReports.Engine.PrintOptions.set_PrinterName(String value)
   at CrystalDecisions.CrystalReports.Engine.PrintOptions.Copy(PrintOptions src)
   at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename, OpenReportMethod openMethod, Int16 parentJob)
   --- End of inner exception stack trace ---
   at CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception e)
   at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename, OpenReportMethod openMethod, Int16 parentJob)
   at CrystalDecisions.CrystalReports.Engine.ReportClass.Load(String reportName, OpenReportMethod openMethod, Int16 parentJob)
   at CrystalDecisions.CrystalReports.Engine.ReportDocument.EnsureLoadReport()
   at CrystalDecisions.CrystalReports.Engine.ReportDocument.get_FormatEngine()
   at CrystalDecisions.CrystalReports.Engine.ReportDocument.PrintToPrinter(Int32 nCopies, Boolean collated, Int32 startPageN, Int32 endPageN)
   at PrintToPrinter.Form1.Button1_Click(Object sender, EventArgs e) in C:\Crystal\CRNET\vbnet_win_printtoprinter\vbnet_win_printtoprinter\Form1.vb:line 91
OK
Edited by: chanpyvivian on Mar 30, 2010 6:18 PM

ITunes 9 Home Sharing does not work on Windows 7 x64

iTunes 9 Home Sharing does not work on Windows 7 x64.
Getting the following error message:
Home sharing could not be activated because this computer is not authorized for the account "iTunes account." Please authorize this computer and try again.
This is a bug since my computer is authorized in iTunes and there is only 2 computer authorized for my iTunes account, so I have 3 more left till I should get this message.
I've just upgraded my iPhone to OS 3.1 using it this morning.
Please advise.
Environment: Windows 7 x64, HP TouchSmart tx2-1020us Notebook
Ivan Farkas
<edited by host>

I am using Windows 7 x64.
I am running iTunes 9.0.2.25
I am running Mcafee.
I can see and play music from the iTunes installation on my Windows 7 machine, but I CANNOT access the library to copy songs from this computer to other computers on my network.
YES, I have enabled "Home Sharing" using my iTunes account. NO, I have not authorized more than 5 computers on this account.
I believe this to be a Windows 7 related issue, as Home Sharing worked as advertised when I was using Vista (before I upgraded to Windows 7).
I CAN set up Home Sharing on two other (host) computers in my home network and it works. These computers are XP and a MacBook Pro. I CANNOT access my Windows 7 machine x64 to COPY music from one autorized library to another. Please help!!!
P.S. - I have attempted to get this to work by turning OFF my McAfee firewall. Windows firewall is disabled.
Message was edited by: turcott

Re: HP 15-d053sr drivers for Windows 7 x64 not installed

Hello!
I have the same problem!!!
Notebook HP 15-d053sr, Product No. F7R72EA#ACB, Serial No. [edited by Moderator], Bios Version F.11
On clean install Windows 7 x64, Can't install all Chipsets, USB 3.0 and Video drivers! Error message: "This computer does not meet the minimum requirements for installing the software"
On clean install Windows 8.1 x64 Can't install "IMEI" (sp64344) driver and maybe more!
HP Support Assistant find only 4 drivers (Atheros Bluetooth, Wireless LAN, Synaptics TouchPad and Realtek Audio drivers)...
Need working, supported, compatible drivers for Windows 7 x64!
Please HELP!!!

Hi @Ainars_LV ,
Thank you for visiting the HP Support Forums. I'm sorry to inform you that your post has needed some editing to remove personal information such as the Serial Number in your Post. From our Rules of Participation:
Protect privacy - yours and others'. Don't share anything about yourself that you would not want to see on a road-side billboard. Don't post contact or other personal information-your own or anyone else's-or any content that you receive in one-to-one communications without the author's consent. For example, don’t post your computer’s serial # or contact information publicly, and do not allow someone you don’t know to remotely take control of your computer.
If you need people to contact you directly, either ask them to send you a private message or subscribe to the thread so you will be notified when there are replies. You may also click on your name anywhere in the forum and you will be taken to your profile page, where you can find a list of threads you have participated in.
Sharing personal email addresses, telephone numbers, and last names is not allowed for your safety. If you have any questions feel free to send me a private message in reply.
Thank you
George
I work for HP

EMET v4.1 not installing on Windows 7 x64

We are testing EMET v4.1 in our environment, and I created a package in SCCM 2007 using the recommended command line from the documentation:
msiexec /i "EMETSetupv4.1.msi" /qn /norestart
When pushed to a Windows XP x32 system via sccm it worked fine to install, and then we configured the settings using the custom ADMX template, and everything is working great.
When pushed to our Windows 7 x64 system's via SCCM it keeps failing, so I tried installing manually and we get the message:
"The advertised application will not be installed because it might be unsafe. Contact your administrator to change the installation user interface option of the package to basic"
Does anyone know why the EMET msi is causing this when set to install using the /qn switch? We use this switch to install many other .msi's via SCCM and have never had this issue before, this seems very weird with a Microsoft branded .MSI.
I changed the /qn to /qb as the message indicates and then we get a message that .net 4 framework is not installed. We have the
Microsoft .NET Framework 4 Client Profile (4.0.30319) installed on our Windows 7 x64 image, I don't see any guidance regarding exactly what version of .net framework is required, does anyone know if the full/extended version is needed
or a newer version?

If you choose "unblock" from the MSI's file properties dialog, redistribute to your DPs, and try to install again, does the issue go away?
Jason | http://blog.configmgrftw.com
I did notice this on the MSI, I will try this and see if it makes a difference. However I did try to just install it locally using the same switches, with the MSI having been unblocked and I still got the same thing. But I will double check this.
Also does anyone have any insight on what .net is required for EMET? I'm going to try the Full .Net 4 framework, since we only have the client profile installed right now.

Windows XP x64 RC1 on a RAID-0 array?

Similar Messages

Maybe you are looking for