Il y a quelque jours, j’ai reçu un ordinateur portable Gericom Overdose 1360e pour maintenance, mis à jour et réparation. Première étape consistait a augmenter la RAM, donc j’ai remplacer la RAM par une barrette de 1Go DDR Sodimm. L’entretien du Windows a été un peu long, car après l’installation de Service Pack 3 sur Windows XP Édition Familiale, il a fallut Défragmenter le disque dure…

FAULT IN NON PAGED AREA

Un erreur rencontré, était par rapport a la mémoire virtuelle. L’erreur a apparue sur un écran bleu. La solution est de vérifier l’état du fichier PAGEFILE.SYS . Il faut que la taille du fichier PAGEFILE.SYS , soit au moins 1.5 fois la RAM installée. Ceci est a définir dans:

Panneau de Configuration > Système > Avancé > Performances > Paramètres > Avancé > Modifier

Une fois dans la fenêtre “Mémoire Virtuelle”, choisissez le disque principale de votre système, et choisissez l’option “Taille gérée par le système”.

Autre manipulation importante a effectuer est d’effacer le fichier PAGEFILE.SYS . Ceci entraîne l’utilisation de l’éditeur de registre. Exécutez la commande “regedit” dans l’outil d’exécuter ou dans l’invite de commande.

Une fois dans l’éditeur de registre, naviguez au clé:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

et changez la valeur de la clé “ClearPageFileAtShutdown” de 0 à 1.

Puis ARRETEZ votre ordinateur. (Boutton Démarrer > Arrêter l’ordinateur > Arrêter )

Maintenant votre PAGEFILE.SYS a été effacé, donc remmettez la valeur de la clé du registre à 0 pour accélérer l’arrêt de votre système.

Si le problème persiste, vérifiez le disque dur, en effectuant une défragmentation avec UltraDefrag, et ensuite vérifiez vos barrettes de RAM, car ceci peut provenir des problème hardware. Pour les anciens, veuillez passer de FAT à NTFS pour le format de votre disque dur. Probablement la réinstallation de Windows pourrait résoudre le problème, si ceci provient des conflits logiciel.

Pilotes Gericom Overdose 1360

D’après beaucoup de recherche, et après avoir contacter le service client de Gericom Allemagne, les pilotes du Gericome Overdose 1360 sont disponible pour téléchargement sur le site de téléchargement de Gericom sous le nom de G557. Voici les liens:

• Pilotes Graphique pour Gericom Overdose 1360
• Pilotes Touchpad pour Gericom Overdose 1360
• Pilotes LAN pour Gericom Overdose 1360
• Pilotes Son pour Gericome Overdose 1360
• Pilotes Wifi pour Gericome Overdose 1360 (Ou sur site du constructeur de la carte wifi RalinkTech: cherchez (RT2500) )
• Pilotes Modem pour Gericom Overdose 1360
• Tout les Téléchargements
  

BIOS Gericome Overdose 1360

Mettre à jour un BIOS (surtout sur un ordinateur portable) est très risqué. Donc vous serrez entierement responsable des conséquences.

Vous pouvez utiliser la mise a jour du BIOS pour le G557 (d’après le service client de GERICOM Allmagne) voici le lien de téléchargement:

http://download.gericom.com/NOTEBOOK/Overdose-Serie/Bios_G557/

Lisez le fichier AFUWIN.txt pour plus d’information.

Meilleur conseil que je pourrais vous donner, c’est d’acheter un nouveau ordinateur portable avec les configuration récentes du marché..

C’est le mode de contrôle fondamental d’un ordinateur. Ce dernier prend ses données d’entrées en ligne de commande, qui sont transmises à l’interpréteur en mode interactif.

Son rôle est de traiter les commandes tapées au clavier par l’utilisateur. Ces commandes, une fois interprétées, auront pour effet de réaliser telle ou telle tâche d’administration, ou bien de lancer l’exécution d’un logiciel.

L’invite elle-même consiste en quelques caractères, en début de ligne (généralement, le nom de compte de l’utilisateur, et/ou l’unité logique par défaut, et/ou le chemin par défaut, et/ou date, …), se terminant par un caractère bien connu (souvent « ] » ou « > »), invitant l’utilisateur à taper une commande.” [1]

Ouvrir une “Invite de Commande”

Sur votre clavier, appuyez sur la touch “WINDOWS” (entre ALT et CTRL) et cliquer sur la lettre “R” du clavier.

La fenetre intitulée “Executer” apparaitra,

Tapez “cmd” et cliquez sur “Executer”,

Vous avez maintenant une “Invite de commande” soit un “SHELL”.

Ref:

[1] – http://fr.wikipedia.org/wiki/Interpr%C3%A9teur_de_commandes

This topic is researched, tested and written by Amir Hossein Moradi.

This is the third article on the Windows Delayed Write Failed error occurring with hard drives (mostly external ones with USB/Firewire/Network connections). On 28th December 2007, I wrote the Windows – Delayed Write Failed – Solved! article which had more than 190,000 views, and helped many users till date. On 9th June 2008, the second article on this topic – Windows Delayed Write Failed – Latest Solution – which had more than 34,000 views till date, was out and is still getting many users out of trouble.

Now, it’s time to write the 3rd article and sum up all possible solutions for the Windows Delayed Write Failed error.

About Delayed Write:

Windows uses a special subsystem for certain disk functions, which caches write operations and performs them when the system is idle. This can improve system performance, but it’s typically turned off by default. The term for this kind of operation is “delayed writing”.

You can see how write-caching is handled for a particular volume by right-clicking on the icon for the drive in the “Disk drives” subtree of the Device Manager and selecting the Policies tabs. The options typically are “Optimize for quick removal” (everything is written to the drive immediately) and “Optimize for performance” (writes are cached).

About the error:

“Windows Delayed Write Failed” error occurs usually when the caching process gets interrupted or the files to be cached get corrupted, either because of a drive failure, a cable failure, or a USB interface fail!

This error might happen to brand new drives as well as good working old ones.

Cause:

This error might be caused by several factors:

• Cache settings
• System Restore settings
• Device drivers
• Media error, drive failure
• USB/Firewire host controllers
• Drive overheating
• Mis-configured BIOS settings
• Ultra Direct Memory Access (UDMA) mis-configuration
• Unmatched cables
• Faulty cables
• Memory parity conflict
• Power management drivers

On the next page(s) I’ll discuss all the working and possible solutions to this issue.

]]> http://www.gibni.com/windows-delayed-write-failed-solutions/feed 18 http://www.gibni.com/windows-delayed-write-failed-2 http://www.gibni.com/windows-delayed-write-failed-2#comments Mon, 09 Jun 2008 22:19:44 +0000 Gi http://www.gibni.com/?p=120 Continue reading →

]]> UPDATE: Latest article: Window Delayed Write Failed – Solutions –> 

A while back, I wrote a post about the “Windows Delayed Write Failed” error message, and I presented ways to resolve the problem. That worked for many people.

Recently, after installing a fresh copy of Windows XP (with SP3), I got the same problem, and I tried everything I knew to solve it, but no luck!! As the problem’s to do with the USB caching and data transfered from the cache to the disk, I went to my favorite search engine again!

The last thing I found, which solved the problem is to use a piece of software from SysInternals (actually aquired by Microsoft) called Cacheset !

Easy Steps to do:

- Download Cacheset.zip from my Downloads Page,

- Extract it somewhere on your computer,

- Run Cacheset.exe from where you extracted the file,

- Click on “Clear” button to clear the current working cache.

- Set the maximum working cache to either 64 MB or 128 MB,

- Click Apply.

- Buy me a coffee if this worked for you!  (Link is in the sidebar)

I tried it and now, after one week of intensive tests, I didn’t get the Delayed Write Failed error! I suppose that the problem is solved.

Anyway, if it happens even after setting the cache, do the same process of cache setting (to 64 MB or 128 MB) again as Windows has tendency to go back to its initial configurations.

Note1: Test both the cases; 64 MB as cache and then 128 MB, if you get your disk working on 128 MB, so keep it, as it runs faster.

Note 2: When applying the “Working set maximum” value in Cacheset, calculate the number by multiplying the required cache by 1024. example:  64*1024=65536 which is the value you should give.

PLEASE GIVE FEEDBACK!

This is tested and it works! Digg it if useful.

UPDATE : Latest article: Window Delayed Write Failed – Solutions –> 

Microsoft released Internet Explorer 8 Beta 1 recently.

Today, I installedit on my Windows XP Professional Service Pack 3, and now it’s been 3 hours I’m testing it.

So far, I’m not so happy with it. It’s a bit slower and does not look so different.

Page formattings are different on IE8, as the same websites on IE7 are better looking! Paraghraph indentation is messed up in IE8.

The new Yahoo! Mail interface does not recognize IE8, and if you try to get in anyway, you won’t be able to read your emails because you can’t access the “folders” as such object is not authorized!

On Facebook, to confirm requests as friend requests, IE8 gets very slow when you click the confirm button as it looks like a “Not Responding” application for a while and then it gets alive again!

Something new that I liked is the “Activity” feature. When you select a text on the screen a small arrow button appears and you can do many things with it like send it with Hotmail, or Blog about it on Live Spaces and other features.

Other thing is “View selected source” which is a feature already there in Firefox for years. With which you can view the source of the selected page element.

I liked the “Translate with Windows Live” activity, which opens a small inline popup with the translation to the default language which you can change too.

IE8 gives you the possibility to create your own Activities as it uses XML files to deal with different activities.

Some few graphics improvements have been done on IE8 including the “You have opened a New Tab” page, the “Quick Tabs” page.

The “Manage Add-ons” section have been changed and it look a lot better and more comprehensible and easy to use.

Microsoft change the “Phishing Filter ” to the new “Safety Filter”.

Well, now it’s been just a while that I’m using IE8, I’ll write a more detailed review later.

But till now, in overall, I’d give a 4 out of 10 to IE8.

You can download and test IE8 from Microsoft. Here’s the link:

http://www.microsoft.com/windows/products/winfamily/ie/ie8/getitnow.mspx

Now You can Download Windows XP SP3 directly from Microsoft!!

That is a standalone service pack 3 update, and is not the whole Windows XP operating system.

I personally do not recommend slipstreaming the service pack, because of few version conflicts on ms dll files.

So just download and install the Service Pack 3 of Windows XP on your system before anyone else!

PLEASE Read throught the article before downloading…

The download link is  at the end of the article

This Blog is written in two languages. / Ce blog est en deux langues.

 ========English========

On 19th of February, Microsoft released a new Release Candidate of its Service Pack 3 for Windows XP

The exact version is Windows XP Service Pack 3, Release Candidate 2 Build 3311

This new service pack provides

-10% increase in performance

-Network Access Protection (taken from Vista)

-Black Hole Router Detection

and a lot of updates and hotfixes which came after the SP2 till date.

The download size is about 315MB.

Microsoft put the public release date in the first half of 2008.

Be aware that SP3 is still in beta version, so think twice before updating.

 ========Français========

Microsoft le metra en public dans la première moitié de 2008.

Soyez conscient que SP3 est encore en version bêta, donc réfléchissez bien avant de proceder à la mise à jour. 

 =============================

DOWNLOAD SP 3:  (All directly from Microsoft.com)

Windows XP SP3 Build 3311 (ENGLISH) : Download 

Windows XP SP3 Build 3311 (German) : Download

Windows XP SP3 Build 3311 (Japanese) : Download

Script to be able to get SP3 through Windows Update : Download

UPDATE 1: New post with new solution: Click Here

I bought a 500 GB Western Digital My Book Premium external hard drive. For few days, everything was working fine, but suddenly the Delayed Wrifte Failed error started to pop up and my drive was no more accessible. Here’s the error displayed on Windows:

“Windows – Delayed Write Failed : Windows was unable to save all the data for the file X:\$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.”

I searched a lot but nothing came up. I had to restart the drive, disconnect and reconnect it again to make it work which was a lot of pain!

Well, before we get to the working solution (for my case), read and see the following :

UPDATE 2: Latest article: Window Delayed Write Failed – Solutions –>

UPDATE 1: New post with new solution: Click Here

I bought a 500 GB Western Digital My Book Premium external hard drive. For few days, everything was working fine, but suddenly the Delayed Wrifte Failed error started to pop up and my drive was no more accessible. Here’s the error displayed on Windows:

“Windows – Delayed Write Failed : Windows was unable to save all the data for the file X:\$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.”

I searched a lot but nothing came up. I had to restart the drive, disconnect and reconnect it again to make it work which was a lot of pain!

Well, before we get to the working solution (for my case), read and see the following :

From Others:

According to the article “8 common causes for ‘delayed write failed’ errors” by Serdar Yegulalp , from SearchWinIT.com which was published on 01.05.2005,

Windows uses a special subsystem for certain disk functions, which caches write operations and performs them when the system is idle. This can improve system performance, but it’s typically turned off by default. The term for this kind of operation is “delayed writing”.

You can see how write-caching is handled for a particular volume by right-clicking on the icon for the drive in the “Disk drives” subtree of the Device Manager and selecting the Policies tabs. The options typically are “Optimize for quick removal” (everything is written to the drive immediately) and “Optimize for performance” (writes are cached).

The first option lets you quickly disconnect drives — for instance, hot-pluggable USB “pen” drives — without first disconnecting them via the Safely Remove Hardware icon in the system tray. If all the options are grayed out, this means write-caching is probably handled at the discretion of the device driver. (You can see more information about the way the defaults for write caching work in the Microsoft article, “Windows XP and Surprise Removal of Hardware“.

In Windows XP, the system may pop up a “Delayed Write Failed” notification balloon, which means that something has gone wrong with the delayed-write system. This does not always mean there has been a fatal problem, but you should take it seriously.

Some common reasons for a delayed-write failure are:

1. Problems with a device driver, especially a SCSI or RAID device driver. Some RAID device drivers are known to issue spurious “Delayed Write Failed” errors in XP Service Pack 2. Most manufacturers have been alerted to this, so check to make sure the disk drivers are up-to-date.
2. Cabling problems. A faulty or broken cable — especially for an external USB or Firewire enclosure—can generate this error. It can also happen if the cable is too long, or if it is hooked up through a hub that isn’t up to spec. Another possible culprit is if you have a UDMA drive that requires an 80-pin cable, and you are using a 40-pin cable.
3. SCSI termination errors. This has become less likely with the advent of self-terminating SCSI hardware, but it shouldn’t be counted out.
4. Media errors. This is the worst possible scenario — essentially, drive failure. If you can garner statistics on the drive via SMART (such as SMART & Simple (http://www.beyondlogic.org/solutions/smart/smart.html), you may be able to determine if there’s a mechanical failure in the offing. Gibson Research’s SpinRite tool (http://grc.com/) is also useful for assessing media errors, but be warned: It may take a long time to do a thorough test.
5. BIOS settings on the computer are forcing faster UDMA modes than the drive controller can handle. This is unlikely, especially with newer hardware (which can support UDMA far more flexibly), but it can usually be fixed with a BIOS upgrade, or by resetting the BIOS entries for the hard drives to auto-detect settings. Devices set to UDMA Mode 6 that produce this error, for instance, might need to be set to Mode 5.
6. Controller issues. I’ve observed that USB controllers that contend strongly with other hardware can produce this error. In systems that have both “long” and “short” PCI slots (i.e., 64-bit and 32-bit), try moving the USB controller to the long slot. Older PCI cards will not fit in such a slot.
7. Memory parity issues. If the problem appears after installing new memory, the memory in question may be faulty or not of the correct type for the motherboard in question. (This may go hand-in-hand with other problems such as random lockups, too.)
8. The LargeSystemCache Registry tweak and ATI video adapters. One peculiar set of circumstances that has been observed on multiple machines with ATI video adapters and more than 512MB of memory involves the LargeSystemCache Registry setting, a DWORD entry found in: HKEY_LOCAL_MACHINE >SYSTEM >CurrentControlSet >Control >Session Manager >Memory Management

   This setting governs the amount of memory set aside by the system for certain kernel processes. If it’s set to 1 (which allegedly improves performance on systems with more than 512MB of memory), it can cause data corruption on some systems, and produce the “Delayed Write Failed” error. Try resetting it to 0 if it’s been set.

Now that you have read the 8 common causes for this error, let’s see about what worked for my case.

Recently I found another solution to this problem that really worked for me. It’s on the next page…

]]> http://www.gibni.com/windows-delayed-write-failed-solved/feed 89