Failure Upgrading Monitoring in GMS 2.0.1

We just completed (incompletely) upgrading our Data Synchronizer from 1.2.5.299 to GMS 2.0.1. Everything appeared to go fine for the most part, except the monitoring. The server has been tested, and data is flowing properly, but we cannot get any stats off from the Dashboard.
During the update, there is the following:
shutting down GroupWise Mobility Service... done
Updating prostgres settings... done
Restarting postgres.....failed
done
<the rest of the upgrade goes fine until...>
Updating Monitoring
Failed upgrade monitoring: Failure in: su root -c "rcpostgresql restart"
done
A reboot of the server has postgreSQL working fine. However, we can't get our monitoring working until we can let the system restart it. For what it is worth, this was a problem when we were running Data Synchronizer also.
The server originally started as a SLES10, and has been upgraded incrementally to SLES11 sp2.
Any help is appreciated. I am still a Linux newb, so I may need some help in that area also (command-wise). Thanks in advance!

Ok, I apparently can't find where to update my thread either. I did some searching on the forums, and found TID 7008132. I added the following lines to my pg_hba.conf file:
local all postgres ident sameuser
host all postgres 127.0.0.1/32 ident sameuser
host all postgres ::1/128 ident sameuser
Now, what that did, was that it enabled postgresql to restart properly. What it also did was bork the rest of gms. When doing a "rcgms start", I had some errors. It said:
Checking for gms monitor: unused
Checking for gms config: running
Checking for gms engine: dead
Checking for gms web admin: running
Checking for gms agent manager: running
Seeing the "dead" on the gms engine, I removed the lines and rebooted the machine. Everything came back up so it now reads:
Checking for gms monitor: unused
Checking for gms config: running
Checking for gms engine: running
Checking for gms web admin: running
Checking for gms agent manager: running
Monitor is still unused, but I believe that is due to the update.sh script not being able to restart PostgreSQL, and erroring out on the Upgrading Monitor section.
To me, this all screams user or permissions, but I don't know where to begin for that.

Similar Messages

Windows 7 Authentication Failures in Monitor Mode on ISE 1.2

Hi Support,
I have a configuration whereby most of my Windows endpoints are not running DOT1x yet. We eventually intend to authenticate them via AD and looking to push out the Windows DOT1x client to all live users soon. Currently users are getting network access due to the fact that all ports have "authentication open" set and the default Authz policy is set to Permit Access (we arent using MAC address endpoint tables to allow MAB etc)
I now have my first test group of users using DOT1x and they match a specific AuthZ policy I have added that checks for their specific AD group on the AD. All is fine.
However I have just added DOT1x to a second test group of users who currently do NOT have any specific matching AuthZ policy (they are on the same AD server but in a diffferent group which I have not defined a policy for yet), and I was expecting they would still join using the default Authz policy. However they do not and on closer observation using "ipconfig" their adapter displays "Media Unauthenticated". I researched this and found that the Windows endpoint can set this condition if you disable the "Fallback to Unauthorized Network" check-box in their dot1x settings. Now I could easily check this box but don't understand why I need to as I surely should be hitting the Default AuthZ policy. However when I debug the switch port I am getting the following:
%DOT1X-5-FAIL: Authentication failed for client (xxxxxxxxxxx) on Interface Gi2/0/26 AuditSessionID 0A540201000064AD8FC27A96
This appears to suggest my AuthC is failing (rather than AuthZ or is the word Authentication a bit vague here?), so here is my question:
1. My AuthC DOT1X policy looks at the Identity Source Sequence that includes the AD server that contains specific groups for BOTH my first test group and my second test group. Users from my first and second test group seem to be hitting this AuthC rule according to ISE.
2. My AuthZ policy contain a specific policy for my first test group ONLY, but the final Default Rule is set to Permit Access. From the ISE persepctive ALL users in my second test group are actually successfully getting this policy. The Authentication Troubleshooting page shows them getting the DOT1X AuthC policy and the Default Rule AuthZ policy. However the message in the switch debug suggests a failure and with my Windows DOT1x client settings as above, the adapter is therefore effecitvely disabled.
3. All this is occuring in Monitor mode, which I thought was harmless provided I dont give additional attributes (VLAN, ACL) to the profiles!
Very confused!
All help welcome
Mark

Please provide us with your Event Viewer administrative logs by following these steps:
Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file to skydrive or a file sharing service and put a link to it in your next post
Wanikiya and Dyami--Team Zigzag

Display resolution settings not storing since upgrading monitors

We have (2) Mac Pros and since upgrading to larger monitors we have been having issues with the resolution settings not "storing" in display preferences. The computer setups are slightly different, and the monitor sizes and make/models are both different, but the problems are the same:
1) Mac Pro DVI out > VGA switcher > Monitor VGA input
2) Mac Pro DVI out > VGA switcher > DVI switcher > Monitor DVI input
(*Note - I know this whole setup seems ridiculous, but it's the way each of the rooms were hard-wired)
With both machines the problems intermittently vary from the resolution itself changing at random when turning on the machine each day, to the desktop background being about 2/3 the size of the screen, while all of the icons and rest of the desktop being normal sized/extended to the edges of the monitor as it should.
It seems that if we change resolution to anything else, and then change back to the desired resolution, that usually solves the problem.
Does anyone know why these settings won't save?
(*Note - we recently upgraded to Lion, but the issue was there before and after the upgrade.)

You must close the window and save changes to keep them.
You may have a problem with Disk Permissions -- the file may not be available to you for writing.

Application Launch Failure -- Transport Monitor

Since reloading Tiger (and all the updates) early this week, I have started seeing this error upon restart:
Application Launch Failure
The application "Transport Monitor" could not be launched because of a shared library error: "8<Transport Monitor><Transport Monitor><HotSyncLib.PPC>"
Huh? Perhaps this has something to do with my .Mac sync icon spinning forever on my menu bar...
Can anyone translate this foreign language and suggest corrective actions?
Thank you!

Ok so im assuming you ran an archive and install. There should be a folder in Macintosh HD that says Previous Systems (n). n is the number of previous systems eg 1, 2, 3. Open that folder, go to users and open up the shared folder. You can copy its contents to your new shared folder in your new users folder. When you run an archive and install, your shared folder gets moved into the previous systems folder and a new shared folder is created that is empty. You need to fill up that shared folder. Try it out and see if it will work.

RAM Upgrade - Monitor Won't Turn On

I just upgraded my iMac from 512 mb of RAM to 2 gigs. Now when I turn it on, the computer boots but the monitor doesn't turn on. Any solutions?

It would help to know the model identifier of your Mac to figure out the exact specs for the RAM; here is how to find it (compliments of OWC - macsales.com):
They are also an often recommended source for RAM; I would check their website before purchasing PNY.

G3 10.3.9 & Itune upgrade - monitor say "out of range" - Please Help

Please help. I have G3 with 512Ram. I've been running Panther totally rialiably for a year and last night I decided to upgrade to 10.3.9 & the latest itunes. The 10.3.9 upgrade went fine and the G3 restarted and ran perfectly but after the itunes upgrade the G3 tries to restart but the monitor turns black after the start tones and comes up with the message "out of range" refereing to the frequences. I can't do anything to get past this message. Is there anyway I can get past this message to reset things? I have the Panther discs and I don't mind loosing my data but I don't want to loose my G3. Are there any keys or proceedures to get me back to square one? I've pressed every key on the keyboard & nothing happens. Please help...I love my G3

Stay calm. This is a minor problem. Do not initialize your Hard drive.
The message saying "out of range" comes DIRECTLY from your monitor, not from Mac OS X. But the reason it appears is that Mac OS X has become confused about what frequency your monitor should be running at. This often happens when the System Parameters -- stored in Parameter RAM and backed up with a small battery -- become corrupted.
The corruption can happen "just because" or it can happen when the Backup battery is forced to work (by loss of main power) but is not strong enough to do the job. If you cannot remember when you last changed it, now is probably a good time.
To get back in business, in the short run, you should reset the PRAM:
2238- Resetting your Mac's PRAM and NVRAM
If a power fluctuation or outage precipitated this problem, the next time it happens will likely cause it again, so replace the 1/2 AA size 3.6 Volt non-recharging battery at your earliest convenience. More info here:
http://www.academ.com/info/macintosh/

After Leopard upgrade, monitor flickering/distortion on startup

I'm at work on a G5 PowerPC Dual 2GHz, OS 10.5.6.
After upgrading to Leopard in a different studio, and then switching this CPU to a studio with two Samsung 214T 21" Monitors connected via DVI, a problem has started. When starting up, both monitors show a distorted desktop display. The displays both show the same broken up vertical columns, about 3 inches wide, and every other column shows a sliced-up portion of the desktop. Also there is weird zigzag flickering in some columns. As soon as I select any monitor resolution, or turn on mirrored displays, the monitors act fine. It seems like it may be a sync-type of problem but I'm not sure. I do not know if this is a Leopard problem or not but I think it is.
This problem did not happen in the original studio when the CPU was upgraded to Leopard. That studio had two Samsung VGA displays connected with DVI adapters.
Please note that I tried resetting PRAM, I gave it 4 chimes.
Also note this CPU is used for sound editing, It has Pro Tools HD hardware, as well as a recently installed Blackmagic Decklink PCI video capture board.

thanks for trying to answer my question. I'm trying to understand your suggestions.
About Antivirus, I have Clam AV installed in Windows. But I haven't been able to run Windows (from a boot) since installing Leopard. I don't see how the mere existence of a program on my Windows disk could have affected my boot sector. Nor do I see how I could do anything about this problem were it true, since I can't boot into Windows! BTW, I did zap NVRAM earlier today while trying to deal with a wake-from-sleep problem, and I haven't been able to dual-boot since then. Are PRAM and NVRAM two separate items? If so, how would I zap PRAM?
I also don't see (but please enlighten me) how uninstalling Parallels would help me. Parallels installs Windows in a virtual disk OR can make use of a native installation of Windows if it exists. In fact, you can boot into Windows without owning a copy of Parallels.
I suspect that the problem lies elsewhere and would love to know what the issue is.
Message was edited by: [email protected]

Need to Upgrade Monitor - Photographer Worthy - Pocketbook Friendly - Recommend

Hi have an HPE H8-1242 quad core i7.
I need to replace the monitor HP sent with the machine. Im a photographer and ive noticed that this monitro changes color and brightness if I move off dead center viewing. If I tilt the monitor back just a bit...the images look radically less brite...same with side to side.
The monitor I have now is a 23 inch HP x2301 Thin Line for $175.
I need a much better monitor from HP that is more suited to Photographers making valuable image judgements and adjustments. It should have a wider viewing angle...a good range color gamut...be able to be calibrated with a spyder pro monitor calibrator...and it should be in the $250, $350 maybe $400 range and be approx 20+ inches.
I know I can go to BH and buy a $2,300 monitor if I was a perfectionist. But I dont want absolute perfect...just something pretty good that HP sells and that good photographers feel pretty good about.
Can anyone recommend the moniotr they are using...or know of a good one??
Thanks
Suzzie

Please read the article entitled "TN versus IPS versus VA Monitors". The article breaks down the differences between three technologies used in LCD monitors. TN is the most common and very poor reproduction when viewed off center. Your HP x2301 micro thin LED monitor displays poor reproduction off center because it uses TN.
Some HP monitors to consider;
HP L2401x 24-inch LED Backlit Monitor uses MVA variant of VA
and any of these HP IPS monitors but most notably the HP Z2440w 24-inch LED Backlit IPS monitor. The Z2440w seems to have the best combination of qualities, features, and price.
Frank
{------------ Please click the "White Kudos" Thumbs Up to say THANKS for helping.
Please click the "Accept As Solution" on my post, if my assistance has solved your issue. ------------V
This is a user supported forum. I am a volunteer and I don't work for HP.
HP 15t-j100 (on loan from HP)
HP 13 Split x2 (on loan from HP)
HP Slate8 Pro (on loan from HP)
HP a1632x - Windows 7, 4GB RAM, AMD Radeon HD 6450
HP p6130y - Windows 7, 8GB RAM, AMD Radeon HD 6450
HP p6320y - Windows 7, 8GB RAM, NVIDIA GT 240
HP p7-1026 - Windows 7, 6GB RAM, AMD Radeon HD 6450
HP p6787c - Windows 7, 8GB RAM, NVIDIA GT 240

Upgrade Monitor - Observer Login

Hello,
I'm upgrading a R/3 4.6C system to ECC 6 EHP4.
OS - Linux x86_64 RHEL 4
DB - Oracle 10.2.0.4
SAPUp Version - SAPUP7107_7-20004320
Software Delivery Tool Details:
Client Version - 1.4.0
Server Version - 1.4.0
DSUService
Version - 1.1.6
I connect to the Upgrade GUI through the recommended method of connecting via an Internet browser.
http://<servername>:4239
No problems in doing this. What I've noticed is that the mode of login is greyed out. I can only login as administrator. How do I get the observer mode enabled?
When another user tries to login to the GUI once the Adminstrator is logged in, we get the message "DSUService is locked by user "<username>".
What I'm trying to achieve is my logging in as Administrator while also allowing the option of an observer to login. Is this possible?
Thanks,
Cheng

Hi,
Check below blog to configure/activate observer mode:
/people/kathrin.winkmann/blog/2009/02/09/check-this-out-and-get-an-example-how-to-create-your-own-observer-mode-and-alert-function
Thanks
Sunny
Edited by: Sunny Pahuja on Feb 15, 2010 7:35 AM

Mountain Lion OS a failure upgrade????

I have recently updated my macbook pro to mountain lion..after the update
1)my battery drains fast
2)Safari freezes quite often.
3)At times even a normal page takes a long time to load with a good net connection.
Any1 facing similar problems? I am really blaming myself for doing the upgrade for $20. Since my mac use to work much better than how it is now....Is there any specific settings to be changed or ?? I dont know., I am not a techie or somethign..just use my laptop for normal purpose....
My macbook pro is 2.3 GHz Intel Core i5 with 4gb ram and contains 10.8.3. It will be of great help if someone shed some light and help me...
Thank you.

From the Safari menu bar, select
Safari ▹ Preferences ▹ Extensions
Turn all extensions OFF and test. If the problem is resolved, turn extensions back ON and then disable them one or a few at a time until you find the culprit.
If you wish, you may be able to salvage the malfunctioning extension by uninstalling and reinstalling it. That will revert its settings to the defaults.

I have T410S, advice in upgrading monitor

I have a T410S with the stock, motherboard videocard.
I want to ugrade monitors and have been eyeing those extremely nice 27 inch 2560-by-1440 resolution monitors.
But my question is will I be wasting my money because of the hardware limitations of my laptop?
If so, what would you recommend?
Solved!
Go to Solution.

thanks jin li

Upgraded 10.5.7 & no ext. monitor. I have listed what's been done thus far

Laptop-early fall 2008 macbook. (no upgrades)
Monitor (bought in sept 08 and been working great since)- Samsung 24" 2493HM dvi to dvi (mini)
1. Updated to 10.5.7 on May 15 then shutdown and went to bed.
2. Booted up in the morning and no external monitor
3. Bought new cables, dvi-dvi and the adapter as well but to no avail. Also tried every combo of powering up, booting and switching cables.
4. Brought my computer in to a store and tried 4 monitors and nothing worked
5. Tried the PRAM m’jig
6. Tried resetting SMC
7. Tried safe boot
8. Tried SwitchRex (sp?)
8. Reinstalled 10.5.2 still nothing
9. Wiped out HD and reinstalled everything from my ext.HD to 10.5.6…a few days before I upgraded but still nothing.
Odd thing is, is that I can see the resolutions listed and the monitor self test shows no problems there…hence the trial in the store to confirm that it’s not the monitor.
I’ve been on the phone with apple for a few days and the rep has been helpful and very courteous, but I’m still at square one. They sent off some stuff, I understand it was a log of what was happening those wee hours before this happened.
Please, please, please can anyone help me or suggest anything else I may try?!!

Marlin2 wrote:
I have the early fall unibody macbook, just before the aluminum release. Sorry for the confusion about the display hookup. It's a dvi cable connected to the adapter for the mini-dvi port (I think that's what it's called)
Well, there is still confusion since the unibody and the aluminum MacBook are the same thing. So, you can't have an "early fall unibody MacBook" that was "just before the aluminum release" (since they are the same thing). In any case, I guess you have one of the older white MacBooks and _not_ one of the newer units that use a Mini DisplayPort for the external video connection. If what I surmise is correct, then you really should have posted in the MacBook( black and white) forum:
http://discussions.apple.com/forum.jspa?forumID=1168
In any case, it probably makes little difference since the problem diagnosis and resolution would be similar regardless of which MacBook you have. I guess what you are using to connect to the display is as follows:
White MacBook + Mini DVI-to-DVI adapter -> DVI cable -> computer display
It's beginning to sound like you _may_ have a defective display port on the MacBook. If you've already done a CLEAN install of 10.5.2 and/or 10.5.6 and have reset the SMC and have zapped the PRAM and have tried a second (and known good) adapter and cable and it still isn't working then the graphics port on the MacBook seems to be the only remaining unknown. This assumes, of course, that you've tried all of the above at the same time and on the same configuration of hardware.
However, if you've done some type of archive and re-install of Mac OS X then you may still have some corrupted caches or preferences. In this case you should reference the thread that pancenter suggested. Do this before you try anything else as I've outlined below.
Frankly, you also seem to be a little confused about exactly what hardware and adapters you are using. Thus, I'd take a careful second look at your adapters and cables and make certain that your setup on the computer and display are correct before you assume failure. Also, just because a previous setup has failed doesn't mean you've eliminated everything in that setup as a point of failure. Case in point, it seems unlikely that you tried a clean install of an earlier version of Mac OS X with those other displays at the store. I'm assuming that you tried those displays with the original install of 10.5.7 immediately after the initial failure.
My suggestion would be:
1.) Since your MacBook is still under warranty get Apple involved. Visit an Apple retail store if possible. This is your probable next step (i.e. ignore the below "otherwise").
-- otherwise --
1.) Do a completely CLEAN install of Mac OS X using your original DVD installer disk and don't update to 10.5.7. This can be done on a second, external drive if you don't want to erase what you currently have on the MacBook's internal drive. Do NOT attempt to use this new Mac OS X installation with the display you have at home (Since it sounds like you've already done these steps on your display at home, if not then you may want to try these steps with the display you have at home. But if you do then go back and do a clean install a second time before you go back to the computer store).
2.) Using this clean install (only) go back to the computer store with both sets of cables and adapters and try each in combination with each other on a display that is different than the one you have at home.
3.) Reset the SMC and zap the PRAM prior to each test with new cables/adapters. Do this reset and zap while you have the external display and adapters disconnected. Throw away the cache files as outlined in the post that pancenter provided. Power down both the MacBook and display, connect the display, turn the display on, turn the MacBook on. See if it works, if NOT then go into the Displays preference panel and click the "Detect Displays" button.
If all of the above fails, then you most likely have a defective graphics port on your MacBook. In that case, it's well past time to contact Apple and see about a warranty repair.

Monitoring and troubleshooting in-place distribution point upgrades

I have a shared SCCM 2007 secondary site server that I'd like to upgrade to a SCCM 2012 Distribution Point. I went to the Administration>Migration>Source Hierarchy>Shared Distribution Points and right clicked and hit Upgrade and then proceeded
through the Upgrade Shared Distribution Point Wizard. Then under Administration>Migration>Distribution Point Upgrades, monitored that status, but even though I left it overnight, the status is still "Upgrade distribution point." I checked under
the Monitoring>Distribution Status>Distribution Point Configuration Status and selected the name of my distribution point and noticed that I'd forgotten to add the Site Server's computer account to the local admin group on my Distribution Point Server.
But even though I've corrected that, the status of the upgrade has not changed and there is nothing of note in resource manager indicating that the process is underway.
Are there any additional logs to monitor the progress of the in-place Distribution Point upgrade? Are there any other troubleshooting steps I can do to determine why the status of the upgrade isn't complete?

Hi all
I would like to share my experience with migrating from SCCM 2007 Distribution Points to SCCM 2012. We have in our test environment 39 secondary site systems with the role of distribution points and I wanted to play with the migration feature "Share
Distribution Point" scenario. In the night in which I had prepared the Secondary sites using the migration wizard, 30 of the 39 sites completed in approximately 3 hours with the status "Completed upgrade distribution point". On all distribution
points the same completion date was entered. It seems that a task at specific times in the background check again whether the migration is complete and the status is consolidated. The remaining 9 Distribution Points were then completed almost exactly after
12 hours.
I then inquired about the migrated packages. On the night not a single package came in the status 'Targeted'. After about 12 hours I saw at once that now at least the distribution points were recorded in most packages. The status 'Installed' but got no distribution
point. I then startet at about 10 packages an update distribution job. These then became the status of 'Installed' more than 4 hours later. Then the weekend was between and on Monday morning, no other distribution points were listed as 'Installed'. I checked
local on the distribution point, if all of the packages was converted. This was the case, not only the 10 I have updated. The packages then should be available during deployments, I think. But I have not tested it.
If you have looked at a package converted times more precise, the status of most distribution point is 'Unknown'. I then googled for this situation, and I have found this
article. There seems to be a bug which is currently in a solving process.
For me, there are two solutions for this problem:
1. Waiting for the hotfix and the problem is then solved centrally. By the fact, that we migrate the 340 Secodary Sites in 3 weeks, I don't think that this hotfix will be available.
2. Depending on the number of distribution points and packages it may be helpful if all 'targeted' packages are again updated. In this 'Unknown' status situation I simply do not know if the packages are really available or not.
I found another problem with the Distribution Point migration. Actually with the migration of SCCM 2007 Secondary Site Server to SCCM 2012 remote Distribution Point, an uninstallation of the secondary site server should be performed. We had tested this with
SCCM 2012 RTM and it was working at that time. With the update to SCCM 2012 SP1 here again seems a problem with the migration to be added. In the SCCM 2007 environment, the Secondary Site Server were removed during migration. But not local uninstalled, even
after 3 days.
Conclusion to the Distribution Point in SCCM 2012 SP1 migration:
As always, you just have to have patience until the migration jobs are completed. Certain tasks must then be carried out by hand. In my view, the missing log information is the biggest problem. Without the log information I was blind
during the migration. If you only have a short window for migration and like us, that we need to migrate 340 Secondary Site Server in the production environment, the scenario must be carefully considered. We proof now to not migrate the Secondary Sites with
the Migration Wizzard, but start from the ground up a new installation of Distribution Points followed by the necessary sync packages.
Kind regards Stefan Somogyi

Wlc 5508 ios upgrade in ha mode

I am having 2 wlc 5508 in HA mode, and want to upgrade ios from 7.5 to 7.6
Current IOS file status in primary and secondary.
Primary WLC IOS : AIR-CT5500-K9-7-5-102-0.aes
Standby WLC IOS : AIR-CT5500-LDPE-K9-7-5-102-0.aes
HA WLC ios upgrade procedure is when we upgrade ios in primary wlc it will push to standby wlc and if earlier ios version match it will accept it.
ISSUE : If you check in wlc status detail I have given upper both has same ios version but IOS file are different and currently in HA mode and working.
Now I am trying to upgrade IOS it is not allow me to upgrade it.
Giving below error :
TFTP receive complete... extracting components.
Checking Version Built.
Image version check passed.
Informing the standby to start the transfer download process
Waiting for the Transfer & Validation result from Standby.
Standby - Standby receive complete... extracting components.
Standby - Checking Version Built.
Standby - Image version check passed.
Standby - Transfer failure : Upgrade from non LDPE to LDPE software is not allowed.
Please download AIR-CT5500-K9-x-x-x-x.aes image instead.
Transfer & Validation on Standby failed.
Transfer download failed both on Active & Standby, Please retry download
(Cisco Controller) >
Please suggest how I can upgrade IOS in HA mode.

Primary WLC IOS : AIR-CT5500-K9-7-5-102-0.aes
Standby WLC IOS : AIR-CT5500-LDPE-K9-7-5-102-0.aes
This won't work and you'll see from the error message. Your standby WLC has a particular firmware loaded with LDPE enabled. So first, you need to answer if you need LDPE or not.
Both firmwares has to match, including LDPE. If you need LDPE, the your primary has to be loaded with LDPE before you can proceed. If you don't need LDPE, then you need to downgrade the secondary to non-LDPE version before you can proceed.

P205-6267 - WiFi mysteriously shuts off - Win 8.1 32-bit

I resurrected an old Satellite laptop my daughter was using for a long time as a 'desktop.' Monitor wasn't working. Once I got her a desktop PC, I managed to repair the display, install a new hard drive and install Win 8.1 32-bit on it.
It has been working well for a few months (wicked fast with Verizon FIOS - 35mbps!) but now I'm having a mysterious problem with the internal WiFi adapter mysteriously shutting off for no apparent reason. Sometimes the troubleshooter can turn it back on, sometimes not and I have to reboot. Lately even rebooting doesn't help - it comes up turned off.
I recently had an overheating problem, solved with an air cleaner spray can. I worry the overheating may have damaged something.
I don't know if the adapter is going bad or if it's a Win 8.1 compatibility issue. I could go back to Win 7 32 bit if necessary, but I'd prefer to fix this first, if possible.
Details:
P205-6267
Windows 8.1 32-bit
3GB RAM
Network Adapters:
Intel(r) Wireless WifFi Link 4965AGN
Driver Date 10/7/2010 Version 13.4.0.139
Digital Signer Microsoft Windows Hardware Compatibility Layer
"Update Driver" says the best dirver is already installed.
Device Manager says "The Device is working properly."
I don't mind downgrading to Win7 but I don't want to do all that only to find it's a hardware problem. Any install I do will be a clean install - I don't have or want the Toshiba disks.
Does anyone have any suggestions or thoughts regarding:
Running Win 8.1 on a p205
Troubleshooting a possible hardware failure on the WiFi adapter
Buying / Installing a replacement WiFi unit if it IS a hardware failure
Upgrading the CPU to run 64-bit Windows (that last is extra)
Thanks in advance...
Barry

Just to let everyone know, I downgraded to Windows 7 32-bit and everything seems stable and fine. My guess is there was some incompatibility or insufficiency in the WiFi driver that made it unreliable in Windows 8.

Failure Upgrading Monitoring in GMS 2.0.1

Similar Messages

Maybe you are looking for