/home

Icon

Informations, tips and technics.

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.

Link

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, , , , , , , ,

Recover your Grub boot loader

On my system I have Vista, OpenSuse 10.3 and XP installed. I have recently lost my grub boot loader and because of a bug in the last OpenSuse 10.3 repair option in Yast, I could not repair my system anymore using the DVD or the LiveCD.

I will try a new tool called Super Grub Disk and see if it can recover my Grub bootloader. I will update this post with the result. Of course, if you have some tips and tricks that you want to share with others, feel free to post some comments.

Super Grub Disk

Update

Well, the repair process was a real success and I was able to recover by grub menu in few simple steps! I highly recommend this tool and put it in your Linux Swiss army’s toolkit.

Just download the ISO file from the web site and burn it on a CD or you can even put it on an USB key. There is an img file also for those who want to use a floppy.

For the documentation, just check their web site, the process is really simple:

  • Boot the CD
  • Select in the boot menu the default option
  • Select your language
  • A few key press (some informations about Grub, the use of the tool and some warnings about the fact that Super Grub Disk is not perfect).
  • Select the OS,  ‘Gnu/Linux’
  • Choose the option to repair depending how your knowledge. I have selected ‘Fix Boot of Gnu/Linux’
  • Select your Linux partition
  • The system will then perform some checks and will try to repair the Gub boot loader
  • Reboot and check if your Grub is back.

Really a life saver. Maybe this tool could not resolve all the problems that you can have with Grub and your boot loaders but it’s the kind of tool that you should remember the name if you have this kind of problem in the future.

Please also check this post for simple guide to recover your OS boot with various scenario.

Filed under: Linux, , , ,

Vista shutdown icon shortcut on your desktop

I will not try to justify why or why not having a shortcut to shutdown the computer in Vista directly on your taskbar or on your desktop but I think it still a thing that could be interesting to know.

The first part is really simple to create the shortcut in Vista as you always do. The interesting thing is what command you should use:

  • Shutdown Computer
    Shutdown.exe -s -t 00
  • Restart Computer
    Shutdown.exe -r -t 00
  • Lock Workstation
    Rundll32.exe User32.dll,LockWorkStation
  • Hibernate Computer
    rundll32.exe PowrProf.dll,SetSuspendState

There is another parameter for the shutdown command, the f parameter which seems can be interpreted by force, meaning forcethe shutdown. That could prevent any message that could prevent a proper shutdown (like a process that not responding or an opened document in Word or Notepad)

Ex:

Shutdown.exe -f -s -t 00

Ref :

Filed under: Windows, , , ,

Tool to querying TCP and UDP ports in Windows

On the post about NTP, I have to do some testing to be sure that my Windows server can contact the NTP server on the port 123. NTP use UDP to communicate and here, telnet cannot help you.

But there is a tool from Microsoft called PortQry:

Download PortQry2 from Microsoft 

 and there is also a GUI for this tool.

Download PortQryUI from Microsoft

I found those tools very usefull and can be added to your IT’ swiss army knife.

Filed under: Windows, , ,

NTP on Windows 2003 and Windows 2000

Recently, I had to make sure that all my Windows servers (2003 and 200 standalone and some Windows 2003 servers in a Windows 2003 Active Directory infrastructure) are in synch with a reliable time source, or an NTP server. The NTP server that I had to use is a Linux one already configured. I will post here the links and basic information on how I have achieve this.

– Windows 2000 Servers
I have used a more powerful tool than the Windows’ NET TIME command. It’s called NTPTime and can be found here.

You will then have only to configure some basic settings.

– Windows 2003 Servers clients synchronizing on the Active Directory
Use the following commands:
w32tm /config /syncfromflags:domhier /update
w32tm /resync /rediscover

(Check any errors displayed and also check the Event Viewer)

– Windows 2003 Servers standalone
Those settings have been set in the registry:

* HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\
NtpServer : ip1,ip2
* HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type : NTP
* HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags :
5

Where ip1 and ip2 are the IP addresses of your external NTP server.
Then,
net stop w32time && net start w32time
w32tm /resync /rediscover
(Check any errors displayed and also check the Event Viewer)
– Windows 2003 domain controller (PDC) that synchronize on an external NTP server:
w32tm /configure /manualpeerlist:ip1,ip2 /syncfromfl
ags:manual /update
w32tm /resync /rediscover

Where ip1 and ip2 are the IP addresses of your external NTP server.

(Check any errors displayed and also check the Event Viewer)

Here are the collection of links that help me out:

Hope this can help.

Filed under: Windows, , , , , ,