In my case the problem was fixed after I cleaned up Startup programs with Autoruns utility from Sysinternals.
Just remove those entries that say File not found.
| [ 0 trackbacks ] | permalink | related link
It happened to me number of times... I start Microsoft Money as usual and it informs me that my password is incorrect. Several times I followed my natural reaction and used "Forgot Password" feature. However, my password was right and I actually knew I didn't change it.
The actual reason was some problem on the server. If you try connecting without using online services it will let you in just fine.
When your login fails and you know nobody changed it. Just give it about an hour or so.
Most probably everything will get fixed on its own.
Do not attempt to change your password since you may run into different problems if your passwords mismatch locally and on the MS Money server.
| [ 0 trackbacks ] | permalink | related link
Here is a good site that can help your search for popular Web 2.0 fonts.
Update:
One more site with free quiality fonts.
| [ 0 trackbacks ] | permalink | related link
Here is a great little Windows utility that can extract your .bin files as well as zip, rar, iso, bin, img, ima, imz, 7z, ace, jar, gz, lzh, lha, tar, sit.
It is very quick, simple, and has no ads.
Visit the developer's page for complete list of features and download.
Please donate to projects like this to keep software available and free.
| [ 0 trackbacks ] | permalink | related link
;)
I had to fix one Linux box that was having an issue with its video driver after a performed system update. I don't know the exact pre-history of what happened to it but here is my solution that I compiled after going through newsgroups and pocking into things myself.
1. Make sure you have gnome-session or kdestart scripts available and included in the path to exclude that there are just not parts of your KDE or GNOME missing. If you are using some other Desktop Environment, check its startup script.
For Example if you are using Gnome to install it on Fedora you need to run as root:
# yum -y groupinstall gnome
# yum install gnome-session
2. Diagnosing problems.
If you are running Xorg all information on why your GUI Desktop doesn't start is located in the log file at:
/var/log/Xorg.0.log
It is recreated every time you restart your X environment.
3. Installing ATI Driver:
- Find out what exact video controller you have:
# lspci | egrep -i 'video|vga|display'
in my case it was:
03:04.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
- Download ATI Driver from http://ati.amd.com/support/driver.html
The driver looks as <filename>.run Just do chmod +x and run it.
In my case it is pretty miserably failed.
This is what I used to solve that problem:
- Extract content of the installation:
# ./<filename>.run --extract
It will create a directory with a name that looks like:
./fglrx-install
Find out what Fedora release you have:
# cat /etc/redhat-release
In my case:
Fedora Core release 6 (Zod)
Build required RPMS from /fglrx-install directory:
# ati-installer.sh --buildpkg Fedora/FC6
In my case it generated several RPM's in the directory above:
kernel-module-ATI-fglrx-2.6.20-1.2944.fc6-8.35.5-1.fc6.x86_64.rpm
ATI-fglrx-IA32-libs-8.35.5-1.fc6.x86_64.rpm
ATI-fglrx-devel-8.35.5-1.fc6.x86_64.rpm
ATI-fglrx-control-center-8.35.5-1.fc6.x86_64.rpm
ATI-fglrx-8.35.5-1.fc6.x86_64.rpm
Run rpm -ivh for all of then starting with kernelXXX. The should be run in a specific order but it will tell you what's missing if you do it wrong. it will also tell you what else is missing to complete installation.
You can find EPMs with missing libraries at: http://rpm.pbone.net/
As a last but important thing is that you need to adjust Xorg config file: /etc/X11/xorg.conf
You can find my xorg.conf here as an example.
Note there a part with BusID "PCI:03:04:0"
You will see where the value for PCI comes if you look above at the output of the lspci command.
Other than that the configuration file is pretty self-explanatory.
You will need to find characteristics of your monitor to fill HorizSync and VertRefresh values.
/var/log/Xorg.0.log will tell you if anything is not configured right.
I left commented out DRI parts in the log intentionally. If your card has 3D support you might need to uncomment it.
All systems are different. It may still take hours and hours to tweaking and x-raying news groups and tech forums. However, no matter what it takes, it is extremely rewarding when everything finally works :)
;)
| [ 0 trackbacks ] | permalink | related link
Back Next
Avatar
