Informations, tips and technics.

Catalyst 8.1 are out with AGP patch

A good news for all of us that have a AGP card and DirectX issues with the 4 or 5 previous drivers from AMD. The Catalyst 8.1 drivers are out and the fix for AGP card also (the web page that is fix is unsupported which I found funny but well, if they works…).

I will test them as soon as I can and try to find how they manage to fix the AGP issue.

The links:

Note: The fix is for Windows XP and Windows Vista. For 64 bits versions or to access the general driver download section, go here. 


Filed under: Windows, , , , ,

Error occurred while downloading file SiteStat.xml

When you use McAfee Epolicy Orchestrator and have deployed CMA (Common Framework Agent) AKA McAfee agent or Epo Agent, you can receive this error message when you try to update the agent and when it contact the EPO server:

Le log are located in C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Db\Agent_<server_name>.log:

Error occurred while downloading file SiteStat.xml
Error downloading file \SiteStat.xml, naInet GetLastError() = 0

In my case I was able to resolve this issue because Epo Server or the CMA installation is confused about what IP address to use. On my Epo Server, I have two NICs, one is for the backup network and the other one the normal LAN access.

I have created the Framework package called FramePkg.exe and installed it manually on some servers. The server then reported them as non compliants and each CMA failed to retreive the SiteStat.xml file from the Epo server.

I had to modify the following files on each problematic server located at C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework:

  • SiteMapList.xml
  • SiteList.xml
  • ServerSiteList.xml
  • Stop the McAfee Common Framework service
  • Go the the folder indiacted above
  • Locate for each files indicated above the IP address, check and modify if needed the false IP address of the EPO server and replace it with the good one.
  • Restart the service

Of course, you will have to do this at the server level also. On the EPO server, there are some files you could edit and change the ip address:

  • In C:\Program Files\McAfee\ePolicy Orchestrator, open SiteInfo.ini and modify the value for LastKnownIP (LastKnownIP=<ip address>)
  •  In C:\Program Files\McAfee\ePolicy Orchestrator, open server.ini and add at the end of the [SERVER] section the value ServerIPAddress=<ip address>
  • Restart the EPO services and you should be ok.

After that, if you starts an update session, all should be correct this time.

Filed under: Windows, , , ,

Recover root password in linux

I will post some comments later but here are some interesting links.

Filed under: Linux, , , ,

bash and time calculation

I could be fun to have a little time calculation when executing a script within a crontab job, so here is a small one:

#!/bin/ksh# At script beginning, get day of month.
BDAY=$(date +%e)
# Get time in seconds.
((BTIME=($(date +%H)*3600)+($(date +%M)*60)+$(date +%S)))

# script

# At script end, get the end day of month.
EDAY=$(date +%e)
# Add 24hrs in seconds, if days don't match.
# It assumes run time is not over 48 hours.
[[ $BDAY == $EDAY ]] && DAY=0 || DAY=86400
# Get the end time in seconds.
((ETIME=$DAY+($(date +%H)*3600)+($(date +%M)*60)+$(date +%S)))

# Calculate and print the time elapsed.
print "Elasped Time: \c"
((HOURS=TOTAL / 3600))
((TOTAL=TOTAL - (HOURS*3600)))
print "$HOURS hours, $((TOTAL / 60)) minutes, $((TOTAL % 60)) seconds."

Ref : link

Filed under: Bash, Linux, , , ,

rsync and ssh

I am currently working on a project that involve doing an rsync session to a server using ssh to secure the transfer. I have found very interesting articles to do this and I post them here in case someone want to read them too:

I will try to post my recipe has soon as I can but I hope those informations and link above can help.

Filed under: Linux, , , ,

Happy New Year 2008!

Dear visitor,

I wish you, your friends and family to have a great 2008 year, with plenty of success in your professional an personal life, happiness and of course health. May this year 2008 the year of the accomplishment of all your dreams and hopes.

May also this year give us at last working drivers for Linux and Windows for those having trouble like me to make them work correctly.. 😉

Happy new year 2008!

Filed under: Uncategorized,

Merry Christmas!

Just a word to wish every visitor of this blog a Merry Christmas and a very happy Christmas time! I hope that you will enjoy this great and magic moments with family and friends. I hope of course for everybody some very nice presents (if you have been nice during this year of course). If you have to travel by car, don’t drink and be caution. Take care everybody!

Merry Christmas!

Filed under: Uncategorized

Catalyst 7.12 Windows XP and OpenSuse 10.3

As an Sapphire X1950 pro 512 AGP video card owner, I always try to install the latest drivers from ATI to have an up to date system to work and play with. The past 4 months have been quite frustrating for me because since the 7.7 version, Catalyst drivers on Windows, even if they install fine, does not seems to work at all and fail every DirectX tests.

This seems to be a common issue for the NForce2 chipset owner. I have an ASUS A7N8X-E Deluxe.

Here is my setup

  • ASUS A7n8X-E Deluxe, latest BIOS 1013
  • 2 Gb Ram (Dual Channel)
  • Athlon XP 3000+ (core Barton)
  • Sapphire X1950 Pro 512 AGP
  • NVidia Nforce drivers version 5.11
  • AGP Texture Size : 128
  • Other BIOS settings are ‘regular’, no overclocking, no custom timings.

Right now, only the 7.7 drivers have been working fine with my system.

I have decided to compile here some searches I have made to solve this issue and I hope they will work also for me.

  • They are some issues with Catalyst 7.9 and maybe 7.10 so, try those tricks with the latest versions 7.12
  • If you have an NVIDIA NForce 2 chipset and have the latest 5.11 chipset drivers installed, try uninstall them and install the previous one (the 5.10 I guess) instead. Some user recommand to not install IDE and/or GART drivers. Then install the 7.12 and see if DirectX diags work this time
  • Some users have reported that replacing some files may also help:
    – Install the 7.7 working drivers
    – Locate and copy somewhere the file ati3duag.dll (and also the ati3d1ag.dll) somewhere on your disk
    – Remove the 7.7 drivers
    – Install the 7.12 drivers
    – Go in Safe Mode, then overwrite the existing file with the one that you have just get from previous 7.7 drivers installation
    – Restart and see if DXDiag works this time
  • Some users have reported that settings the AGP Texture Size from 128 to 256 seems to have resolved the issue.

Also, you can test alertnate ATI drivers like the one provided by Omega, see here for download.

I have not tested myself those tricks but I will and I will post the result here.

Ref : link, link2, link3

And for Linux now?

Well I have tested the 7.12 on my OpenSuse 10.3 installation and do a very basic installation. I even deleted the existing xorg.conf in case of, ran a sax2 -a to have a blank, working xorg.conf file, runs then sax2 -r -m 0=fglrx and … they do not work right now: sax2 display a black screen after starting a X server and I need to reboot to have access to my system.

Ok, I will test again and spend more time on the 7.12 driver installation on Linux and I soon as I have a working solution, I will post it here.

Stay tuned.

Update (24.12.2007)

Well, the trick to install previous nforce chipset drivers was not working (at last) for me… I will test the AGP Texture Size and the file replacement trick soon and let you know about the result.

Filed under: Linux, Windows, , , , ,

Catalyst 7.11 (8.433) on OpenSuse 10.3

I haven’t posted yet the procedure to install the latest fglrx drivers on OpenSuse 10.3 simply because I haven’t tested yet.

For those you are looking for some informations about the installation process, you can check this web site.

On my side, I will test them as soon as I can and post here the results.


Filed under: Linux, , ,

Simple guide to recover your various boot loader

Update : See there for some other way to recover your grub-xp-vista bootloader

I have previously posted some tips about boot loaders and I think that I have to right a new post with some steps that you can try to recover your various boot loaders, from Grub, XP or Vista. This is not a complete guide since I cannot guarantee to 100% that it will work in all scenario but maybe it can help. I will take my own configuration as an example:

  • OpenSuse Linux 10.3
  • XP
  • Vista

All installed on the primary disk.

Also, the install order is :

  • XP
  • Vista
  • OpenSuse 10.3

As you already read in a previous post, after OpenSuse 10.3 was installed, all boot entries should works and be available in Grub at this time.

Recover your Grub bootloader

  • See my previous post
    Just remember that there is a bug in OpenSuse 10.3 repair option so I have to use another tool

Your XP entry does not work after installing Vista

  • After installing Vista, your old XP entry is correctly listed in the Vista boot loader but a message appear when you try to boot XP : Can’t find file ntldr
  • Boot on Vista, copy the file from your XP partition boot.ini. ntldr and ntdetect.com to your root Vista partition, that should resolve the issue (just remember that those files may be hidden)

The Vista boot loader no longer work

  • First, use the Vista DVD to boot your system and try the repair options. At least, you should have a recovered Vista boot loader.
  • Sometimes, even if the repair was successful and that you can boot Vista, you XP entry does not work. In this case, check the XP entry for the driver letter. (I will post soon what I have on my machine to make things clearer)
  • To ease the troubleshooting, once in Vista, download and use (make a backup of your bootloader first!) a tool like EasyBCD (link) so you can change some settings more easily.

Error in partition table, unable to repair Vista, XP or Grub boot loader

  • In this case, I had the best results by writing a new and clean MBR to the disk using a tool like TestDisk. You can find this tool with the SystemRescueCD (link). Just select your disk and select the option to reset MRB to zero and install a clean MBR.
  • Once done, try again the Vista repair option and other tips in this post.

Just a note : Sometimes, after writing a clean MBR to the disk, it may be necessary to use first the recovery option from the XP cd to install the XP boot loader first. Just boot using the XP cd, then access the recovery console. From here, use the fixboot and fixmbr options. Please check also the command to find, list an recover your XP boot entry. Once you have done that, you should be able to boot at least XP. Then you should proceed with the Vista repair tips.

That’s pretty all for now. I will try to update this post with more details soon.

Filed under: Linux, Windows, , , , , , , ,