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
Suddendly my MSMoney started to crash on the application start up.
Who could guess but that turned out that it was my new Logitech Mouse that caused it.
I just bought a new cordless laser mouse VX Revolution. Windows installed default drives and everything seemed to be working ok... Strangely enough MS Money was that one app that didn't like my new toy :)
Installing latest Logitech driver didn't solve the problem unfortunately.
If I unplug the mouse I can start the application just fine.
I wonder if there is some sane solution to using both....
Despite the problem it is a great notebook mouse.
+ 
= BOOM!| [ 0 trackbacks ] | permalink | related link
I am not exactly a MS/IIS person. The content of this post is not based on any kind of deep experience. I just had to figure out something when I needed to export/import the IIS configuration... Feel free to leave comments if you disagree with anything bellow.
Export:
C:\WINDOWS\system32>cscript iiscnfg.vbs /export /f ../../IISExport.xml /sp /LM/W3SVC/1 /inherited /children
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Connecting to server ...Done.
Configuration exported from /LM/W3SVC/1 to file ../../IISExport.xml.
Parameters:
.......................
/f [Path\]FileName.xml
/sp SourcePath - Required parameter. Specifies the metabase keys to export. Enter a metabase path, including /lm/ root, to indicate the selected keys.
Format: /LM/W3SVC/n, where n - is instance ID in the IIS metabase.
To find out what is the instance ID of the site you are exporting go to the IIS Manager and click on Web Sites in the left menu. It will show the list of sites and IDs on the right.
Alternatively, you can go to IIS manager and right click on the Web Sites, then select properties.
On the Web Site Tab click properties in the logging section. At the bottom it shows you the log file name. It starts with W3SVCn where n is the instance ID.
/inherited - Adds the inherited properties of the exported keys to the export file. Without this parameter, the export file does not include properties inherited from higher-level keys. If you select this option, iiscnfg.vbs adds the inherited properties of the exported keys to an IIsInheritedProperties key in the export file. When you import keys from this file, you can elect to import the inherited properties with the keys.
Note: When inherited properties are imported, the imported keys retain the properties they inherited in the exporting configuration. If inherited properties are not imported, the keys inherit the properties of the importing configuration.
/children - Recursively adds the subkeys of the specified key to the export file.
Import:
C:\WINDOWS\system32>cscript iiscnfg.vbs /import /f ../../IISExport.xml /sp /LM/W3SVC/1 /dp /LM/W3SVC/111 /inherited /children /merge
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Connecting to server ...Done.
Configuration imported from /LM/W3SVC/1 in file
IISExport.xml to /LM/W3SVC/111 in the Metabase.
Parameters:
.......................
/f [Path\]FileName.xml - Required. Specifies the path and file name of the XML source file.
/sp SourcePath - Required. Specifies the location in the XML file of the keys being imported. Enter the metabase path as it appears in the XML file. To import all of the keys in the source file, enter the metabase path of the root key.
/dp DestinationPath Required. Specifies the metabase path into which the keys are placed. Enter the metabase path as it appears in the XML file.
In the example: /LM/W3SVC/111, where 111 is just a unique key previously not present in the metabase of the target server.
/inherited - Imports the inherited properties of the keys. This parameter is only effective when the source file includes inherited properties.
/children - Recursively imports the subkeys of the specified key.
/merge - Combines keys in the XML file with the existing metabase keys. Without this parameter, the keys in the XML file replace existing keys in the same metabase path. The /merge parameter adds keys to the metabase that appear only in the XML file, retains keys in the metabase that are not in the XML file, and applies the values in the XML file when a key appears in both the XML file and the metabase.
Here is a good article about IIS Metabase structure.
| [ 0 trackbacks ] | permalink | related link
Back Next
Avatar
