Gericom Overdose 1360

Entretien Ordinateur Portable

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:gericom_overdose_1360


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:



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é..

Invite de commande – Windows XP

“Un interpréteur de commandes, parfois désigné par l’anglicisme shell, est un programme faisant partie des composants de base d’un système d’exploitation, le Command-line interface (CLI) (ou invite de commandes).

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.

 windows_button


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


Windows Delayed Write Failed Error – Solutions

Window Delayed Write Failed ? Solutions are here!


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

harddriveicon

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_write_delayed_failedAbout 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_write_delayed_failedAbout 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.

 

write_delayed_causeCause:

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

 

write_delayed_solutionResolutions:

Here are different resolutions to the problem, I’ve arranged them in such a way that the most probable and easy to apply is at the top of the list. Read all resolutions carefully before any attempt on your drive(s) and/or computer(s).

 

1. System Restore Settings:

Users reported that Windows might try to write system restore data on the external drive, or try to monitor the drive in case of a system crash. This procedure might be a cause for the Delayed Write Failed error. What to do is quite simple. Just follow this photo tutorial:

 

Open your Control Panel:

click-control-panel

 

Open System:

control-panel-windows-xp

 

Go to System Restore tab, choose your external drive, and click the Settings button:

System-restore-settings-windows-xp

 

Check the Turn off System Restore on this drive checkbox and click OK:

system-restore-monitoring-settings-windows-xp

 

Now, you need to restart your computer, and if System Restore configuration was the issue, it should be solved.

2. Device drivers:

Some older RAID device drivers are known to cause the Write Delayed Failed issue, so do check with you hardware manufacturer for the latest device drivers.

I suggest that you check for:

  • latest RAID drivers for your hardware,
  • latest BIOS for your motherboard,
  • latest chipset drivers,
  • latest USB hub (host controller) drivers,
  • latest graphics card drivers.

 

3. Overheating:

First thing to try is to see if your drive is not over heating!

According to Seagate, “the operating temperature range for most Seagate hard drives is 5 to 50 degrees Celsius”.[5]

This is true for most of hard drives on the market, either you have a Maxtor, Seagate, Samsung, Western Digital or other brands of hard drive, you should keep it under 50 degrees Celsisus ( equivalent to 122 degrees Fahrenheit)

 

4. Faulty cables:

Check your cables!

Old USB (or FireWire) cables, can be faulty and cause packet loss. Faulty cables can cause severe damage to your hardware, so check your cables and it’s recommended that you buy some new and good quality cables.

 

5. Unmatched cables:

Check your cables, again!

If you got an IDE drive, then you should check the connector to be the right one! You are using a 40-wire connector cable to connect the UDMA drive to the controller instead of the required 80-wire, 40-pin cable! Fix this and you should be finished.

Read this article from Microsoft:  You receive an error message when you save or move documents in Windows XP: “Delayed Write Failed”

 

Remaining resolutions are on the next page(s).

 

Windows Delayed Write Failed – Latest Solution

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 !

cacheset_scr


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

Internet Explorer 8 (IE8)

Download Internet Explorer 8

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!

Continue reading “Internet Explorer 8 (IE8)”

Download Windows XP SP3 Build 3311.

Download Windows XP SP3 Build 3311

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  Continue reading “Download Windows XP SP3 Build 3311.”

Windows – Delayed Write Failed – Solved!

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 :

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 :

Continue reading “Windows – Delayed Write Failed – Solved!”