Jump to content

NATO

Member
  • Posts

    64
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Belgium

Posts posted by NATO

  1. FYI

    Big Brother's 'computer' and www (what a wicked web they weave when they labor to deceive) is based in Biblical thinking which Bill Gates (Retired) is obviously aware of.

    ,95 = 1995 AD

    '98 = 1998 AD

    2K = 2000 AD

    XP = eX Patris (Oh 'father' why hast thou deserted us?)

    VISTA - a landscape with NO religious sheeple. (Check the desktop wallpapers.)

    7 = the Seven headed Monster with ten horns, and other religious connotations.

    8 = The sign for infinity turned 90° into an 8

    9 ??? Deep space 9. (The Council of Nine or Great Ennead of Egypt.)

    No Sun no gravity, no orbit, and planet Earth disappears into the abyss of empty space.

    Time to defenestrate Windows and live life to the full whilst there is still time...

    http://theabysmal.wordpress.com/2007/03/03/december-21st-2012-an-updated-implementation/

    There are now 176 Days to Dec 21st 2012 (00:00:36 Hours)

    Bye Guys, have fun!

    Thanks for all your help.

    Good luck to all of you.

    Ian

  2. Hmmm;;;

    So I used pagefile.vbs to delete the Primary drive pagefile (there is one on the 1st logical as well) and it said success! whatever.

    So I ran analyse in Defrag and it was still there only it had changed from green to blue.

    Unlocker deleted it.

    Wonder if there is any way to pin the pagefile to the back of the partition so as to keep it away from the OS files when defragmenting without using Perfect Disk or some other third party defragmenter.

    The standard defrag plus the addition of Sysinternals Config does a good enough job.

    Diskeeper is to heavy for a 1.0GHz PIII

  3. Drive letters continued...

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer]

    "ShowDriveLettersFirst"=dword:00000004

    This setting - only - shows drive letters in front of names in Explorer.

    However in Defrag and Computer Management the drive letters are still - after - the names!

    Is there any way to make this a uniform setting throughout the system?

    Additionally: If you open say, the system32 folder, and hold down the Ctrl key and then tap the + on the NumPad the columns are sorted semi-automatically.

    Is there any way for the system to do this fully automatically not only in the folders but also in the various listings in Event Viewer, etc?

    Plus.... Is there any way to get the My Pictures folder to always show Thumbnails and - then - to always show the contents of each Thumbnail folder as a Filmstrip instead of having to sort this out every time you open the (My) Pictures folder.

    I wonder what Apple does.... ¿

    :scream: \Ö/

  4. Keyboard layouts are absolutely necessary if you want to type in several languages using different alphabets, etc. They are NOT useless :ph34r:

    I have a different (Military) logic concerning this entire creation.

    One planet one language, one alphabet (the smallest), no expletives, no 'alternatives' no accented characters, right to left only, one currency, ONE keyboard. (AZERTY of course!) and so on.

    Bill Gates has the ONE Windows megalomaniac monopoly logic.

    Or one Window.

  5. I elected to keep the newer files and allow nLite to use the standard method for integrating the updates.

    I noticed that this problematic security update KB2686509 concerning keyboard security appeared to integrate without any problem.

    Why we need 90 keyboards on the one system is a mystery to me so I have asked Susan Bradley if she can fix it to use just the native 409 US OS keyboard and the local Belgian 813 keyboard as per the 12 preloads.

    MS should have made the keyboards part of the Windows Add Windows Components in add-Remove programs IMO along with NT Backup, Movie Maker and System Restore and many other components which people don't use.

    Thanks for your help -X-

    Ian

  6. Downloaded the files and ran nLite to make a fully updated installation DVD with SP3, etc.

    Checked 'report' to see if there were any problems and found that several KB updates were "Not supported" and that some files were older than the files already in the SP3 service pack.

    Will this be a problem when updating online?

    Ran nLite again without checking 'report' and got a bigger .ISO file.

  7. Many thanks -X-, I will try the batch file tonight.

    Nothing else has worked so far.

    Ian

    I will also download all the cabinet files to add to my latest nLite XP Pro SP3 .ISO

    Thank you very much, that is a GREAT help!

    (The batch file didn't work either so I will e-mail Susan and see if she can help.)

  8. Belarc Advisor shows that I just need - one more - update. (Making 128... )

    Q2686509 - Important - details... http://support.microsoft.com/kb/2686509

    And yes, I do get the faulty keyboard file and yes, I have - copied - not moved - the appropriate files from another machine into my system32 folder.

    Still no go. My fault again as I deliberately removed all the keyboard files which I didn't need including the Bulgarian KBDBU.DLL which was acting suspiciously.

    1. Would not be deleted and kept on re-appearing in the MUI cache.

    2. Showed up as being the one file missing when doing a clean install with an nLite .ISO.

    What I would like to know oh greatly esteemed experts is this.

    As MS says that one can remove Keyboard Layouts should I remove all but the two which show up in the Keyboard Preloads (409 US of A, and 813 Belgian Point) and all the corresponding DOS references under these keys...

    HKEY_LOCAL MACHINE\SYSTEM\Current Control Set\Keyboard Layout\DOSKeybdCodes

    HKEY_LOCAL MACHINE\SYSTEM\Current Control Set\Keyboard Layout\DOSKeybdIDs

    HKEY_LOCAL MACHINE\SYSTEM\Current Control Set\Keyboard Layouts\

    AND the corresponding keys, etc. in Control Set 1 and Control Set 3

    Or will I have to put ALL of these dratted keyboard DLLs back in?

    :scream: \Ö/

    Thanks again ;-)

  9. Google each of the various names Rsop Planning Mode Provider, CmdTriggerConsumer, and HiPerfCooker_v1 to try and find the cause. I didn't find the root cause, but these same items have been showing up for YEARS. See here for an example - http://forum.piriform.com/index.php?showtopic=18226. You are not alone.

    Cheers and Regards

    I just happened to do a new install disconnected from the internet and checked the Event Logs.

    The same three entries were present so I am guessing a super Alexa.

    Evidently they are installed when Windows is installed.

    Hmmm.

  10. Maybe you need to use a Recovery Disc CD for Windows Vista.

    Create a Recovery CD

    If you have this one, try to repair the Startup...

    For Windows XP

    Recovery console

    But it seems that you need to change your hard drive, and reinstall the OS.

    Regards

    Just tried the link you give for the Recovery Console and it is in French, which is OK for me but might not suit everyone.

    So if you want an English version with multilingual keyboard support try this site: http://artellos.com/arcdc-page

    If you need a Recovery Console with US English only keyboard try this link: http://www.thecomputerparamedic.com/files/rc.iso

  11. I have given up on this since the 'Distributed Link Tracking Service' changed the primary from C to D and the 1st logical from D to C.

    jaclaz pointed out that it would be difficult to change back and the MS articles did not help any so I just upped the letters on the other drives.

    To: [ D: Primary ]{ [ E: 1st Logical ] [ F: 2nd Logical ] [ G: 3rd Logical ]

    And made the DVD drive H:

    Just had to change the paths to the folders.

    Easiest way out, otherwise I would have to delete all the partitions and re-partition the drive.

    chkdsk still jumbles up the drive order.

    Too bad.

    Thanks anyway and have a nice day.

  12. Knowing you had bad sectors, you should have gone for a full format on that c:.

    Actually one should go through the respective drive manufacturer diagnostics, BEFORE that :angel .

    And possibly re-test with a tool like Victoria or mhdd....

    Then flip a coin, and whatever is the result :w00t: , change that drive, and the new one will crash in two months time. :ph34r:

    Seriously, very few things in my experience are so aleatory as the "expected lifetime" of a disk.

    Once upon a time (many, many years ago) I saved some data from a Samsung HD (a 4.3 Gb one, so you understand how much time has passed).

    The drive suffered from a rather "heavy" head crash which made several HUNDREDS clusters not only unreadable any more but even not formattable (and in theory there should be magnetic debris all over the disk, likely to ruin quickly the whole surface).

    Once I got the data (luckily the actual "important" data was fully recovered) and having installed a new hard disk, I had this "relic" around.

    After a few tests with zeroing out, formatting, wiping, etc. with no result, I set it aside.

    Being (notoriously) cheap ;) a few years later I decided to make an experiment (I needed a small hard disk for a headless "controller like" machine, of course not in mission critical use).

    I simply determined by experiment where the bad clusters were ( a biggish almost contiguous zone around 1/3 of the disk) and simply partitioned the disk in such a way that that zone was left untouched (one partition before and one after the bad zone).

    As per today, that machine (and the disk) is still working allright (and has it worked 24/7 for the last - cannot remember exactly - 8 or 9 years).

    What gives? :unsure:

    jaclaz

    What gives?

    Like a lot of things quality control assigns degrees of perfection/imperfection to the drives.

    Good ones get a 1 and go to government and the military. Not so good get a 2 down to 6 and the cheaper you buy the cheaper you get.

    Government and Military buyers are wise to all this and expect the best.

    Yes, I do use the drive diagnostic and do a burn in test.

    With the first Maxtor drive I did all this and about three weeks later ... click, click, click, click, click ... stop.

    S.M.A.R.T. didn't report any errors either.

  13. For years I had a 12MB bad cluster on the C: partition and that has gone too. (Cured!) :whistle:

    Of course now they're on D: :D

    More seriously, I hope the :whistle: is a sarcastic :whistle: to yourself and not a :yes: to Jaclaz . Otherwise you might be in for a bad surprise in a few months. Better get them back marked as "bad" before your OS tries to actually use them in an unsuspecting way.

    Knowing you had bad sectors, you should have gone for a full format on that c:.

    They are gone now. I always use full format on hard drives.

    Quick format is reserved for USB sticks and my few remaining diagnostic, partitioning and imaging floppies. (All on CDR now.)

    It's a Maxtor drive, just like the first one, which died after a year just outside warranty.

    I have a Western Digital on order.

    One thing that really is annoying about the MS Documents folder is that the other folders are inside it.

    MS should have made separate folders for Documents, Pictures, Music and Video and made it simple for them to be moved to partitions and the Video to a second slave or external drive IMO.

    I move them anyway, as it saves time defragmenting.

  14. @NATO

    don't take this as an offence (as it is NOT meant to be one :)) but you haven't cured *anything*.

    You simply re-installed.

    Medical comparison.

    I cured the gangrene by amputating the affected limb.

    *** You can cure gangrene sometimes by applying unripe Papaya in a compress to the affected area.***

    That's why it is known as the Medicine Tree. Delcious too, reminds me of when we lived in Singapore.

    (GHQ FARELF - Far Eastern Land Forces. 1958-1961)

    jaclaz

    For years I had a 12MB bad cluster on the C: partition and that has gone too. (Cured!) :whistle:

    Three entries in Event Viewer relating to HiPerfcooker and two others adding entries to the Windows Namespace turn out to be present immediately after doing a clean install anyway. Probably some sort of super Alexa. (Learning!) :blink:

    Rootkits which appeared on the E: Music partition have also been taken care of. (Cured.) :whistle:

    Logon/Logoff with this Belgian (Period) keyboard. (Cured.) :w00t:

    Running like a dream thanks to your help.

  15. As expected.

    You were already given the appropriate links to read. (I was?)

    You need to do a number of changes to the Registry when offline, not just the drive letter in Mounted devices, when it is the System drive...

    There is a report counting around 4000 (four thousand) occurrences that need to be changed in Registry and related files:

    http://www.velocityreviews.com/forums/t310287-change-boot-drive-letter-xppro.html

    The use of tools like Registrar: http://www.resplendence.com/reglite

    (i.e. anything that can do a "general" search and replace of the registry) is advised, alternatively, if you want to "risk" the hex approach sketched in the mentioned thread, gsar is a good tool: http://home.online.no/~tjaberg/

    Your mileage may vary anyway.

    jaclaz

    P.S.: if you want to change the drive letter of a XP install (mind you, it is a tricky business) the instructions are NOT these ones:

    http://support.micro...om/?kbid=307844

    but these ones: http://support.micro...om/?kbid=223188

    which, if followed will lead you to a system to which you will not be able to log in, unless you do what is suggested here: http://support.micro....com/kb/249321/

    After having (hopefully) rebooted OK, you will still need to use a tool like registrar lite to find occurrences of D:\ in the Registry and change them to C:\, otherwise some utilities will not work.

    jaclaz

    OK. Thanks,

    I will follow your suggestions to the letter. :angel

    Just have to add the SET command as below for your reference.

    To add Security Configuration and Analysis to an MMC console.

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

    1. Click Start, click Run, then type mmc and click OK.

    2. Do one of the following:

    A. To create a new console, on the File menu, click New.

    B. To open an existing console, on the File menu, click Open, click the console you wish to open, and then click Open.

    3. On the File menu, click Add/Remove Snap-in, and then, in Add/Remove Snap-in, click Add.

    4. Click Security Configuration and Analysis and click Add.

    5. Click Close, then click OK.

    The object is to 'Allow floppy copy and Accessto All Drives and Folders.'

    This will then allow the Recovery Console SET command to become operable.

    Using the Recovery Console type: set allowallpaths = true

    This should then allow the drive letters C & D to be changed into the correct order as per the 2nd MS KB Article.

    My problem was caused by practically cloning the C: drive.

    The drive letter order was changed by the 'Distributed Link Tracking service which re-set the volume I.D.

    Without notifying the operator.

    From: [C: Primary]{[D: 1st Logical][E: 2nd Logical][F: 3rd Logical]

    To: [D: Primary]{[C: 1st Logical][E: 2nd Logical][F: 3rd Logical]

    If this doesn't work out then I will simply re-install from scratch now that - all- the other problems have been sorted out.

    Other than this the system is working very well. The previous install lasted a full ten years, so that can't be too bad.

    Thanks again.

    *************************************************************************************************************

    Turned out to be very easy as the Administration tools Security Policy snap-in is installed with XP Pro.

    Just went to Administration Tools, Local Security Policy and scrolled down to Recovery Console: Allow Floppy Copy and Access to All Drives and Folders, to find that it was in the Disabled state.

    Double-click on the entry to open the panel and click on Enable - Apply - OK

    Went into the password protected recovery console and used: >set allowallpaths = true - to double check, as it had showed up that the set command was disabled at the first attempt.

    No problem.

    Now to try the registry change and Registrar Lite.

    (Re-install looms!) ;-)

    At least I now know what was wrong before.

    :)

  16. Well after a very successful operation to remove root kits and make a new installation on the D (1st logical) partition to transfer to the C (Primary) partition I find that you cannot do this easily when Windows decides to change the drive letters without telling you!!!

    So now I have a primary D and 1st logical C. Arrgg!

    MS suggests that when the system changed drive letters 'without user intervention' that you can change the letters back by editing the registry going to...

    HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices

    ...and scrolling down to the C and D drive entries...

    \DosDevices\C:

    \DosDevices\D:

    Then...

    Re-name C to Z , to free the letter C

    Re-name D to C , to get the right letter back

    Re-name Z to D , to put the partitions back in the right order.

    But the binary data is quite different in these two keys.

    Tried it twice now and just get a BSOD Status 0x0000135 (0x00000000 0x00000000)

    So I just restored the D primary drive from a drive image on F with no problem, as this registry edit doesn't seem to work.

    So here is the plan. Change the C 1st logical drive partiton to Z in Computer Management and remove all data folders.

    Do a dual-boot install to this Z drive and boot up on the Z drive.

    Change the D Primary partition letter back to C

    Re-boot to C (Hopefully)

    Change the 1st logical from Z to D, format and re-place data folders.

    Fingers crossed.

    Anyone got a better solution?

    De-defenestrate Windows maybe???

  17. We all know that you can ClearPagefileAtShutdown by either modifying the registry or setting the ClearPagefileAtShutdown in Security options.

    But this takes time as the system writes zeros to the pagefile.

    Is it possible to completely DELETE the pagefile, in less than one second, so that it can be re-created when the system re-starts?

    Batch file maybe?

    DEL C:\pagefile.sys ???

    But how would you activate it?

  18. Solved. Finally! (And cured a lot of problems into the bargain.)

    As you know from my first post I wanted to make an XP install CD from the installation on the C: drive as I had lost all my original OEM installation CDs.

    So I used the Windows setup.exe on the C: drive to set up a copy on the indentically sized D: partition (1st logical drive). I then booted to this partition and used the MS MUI rollback tool to remove the other languages.

    I then made a drive image of the D: drive with Image for Windows 1.64 and extracted the files from the image to a folder on the F: partition using TBI View (Two really good software tools, among others, from TeraByte Unlimited in Las Vegas) so that I could use nLite to cut it down to size and make an ISO.

    I then formatted the D: partition (1st logical drive) and re-installed a second time from the nLite ISO giving me XP Pro SP2 (OEM) without any unnecessary junk and practically no MUI. (Some keyboards did manage to get past this process but got picked out and deleted from the remaining MUI cache using Reg Organiser.)

    As the SP3 downloaded file turned out to have corrupt .cab files, according to the Avast AV, I downloaded the US SP3 ISO and burned it to CDR.

    I then installed and ran the subinactil.msi tool from MS using the script which they offered and proceeded with the SP3 update which went in flawlessly.

    (Contrary to those who claim that SP2 has to be - fully - updated - before - SP3 will install.)

    I then added IE8 and all my other software from the archive on the F: partition, cleaned and optimised the registry, ran chkdsk, defragged the drive, and telephoned MS USA to validate the install.

    1 - click later, back up and running. :-)

    Just had to go online to update the AV, complete the validation, and add all the many security updates.

    Made a new drive image of the, fully functional, D: drive with Image for Windows to archive and then 'restored' it to the C: drive.

    Re-booted to the C: drive, edited the boot.ini file and formatted the ... 1st logical drive ... in the extended partition ... where the new install ... had been prepared.....

    Login - Logoff works perfectly, as all settings are US English, even with the Belgian (Period) keyboard. (There is a Belgian (Comma) keyboard, but they are quite rare.)

    I now have - NO - 'Teefer' (for NT) and 'wpsdrvnt' (Windows PS2 driver NT) errors in the event viewer as there was no PS/2 keyboard and PS/2 mouse attatched when the initial installation was done and these legacy drivers no longer appear in the hardware device manager. Hooray!

    So - VERY MANY THANKS - to all of you on the Forum for your help, which has proved to be invaluable.

    I hope that some of you might find this helpful in return.

    Hope you - ALL - have a great day.

  19. If you look at the Logon-Logoff thread and the problem of legacy Teefer for NT and wpsdrvnt driver issues you will see that I have cured all the evils which were plaguing this 10 year old installation by making a new nLite install CDR from the old C: drive installation.

    I even have the correct logoff panel instead of the older cream colored one.

    Even the root kit has disappeared with a good formatting.

    I have now reverted to single boot as it was only a temporary situation.

    Problem is that Windows, in its inanimate (?) infinite wisdom, has reassigned drive letters so now the Primary is D: and the 1st logical drive is C:

    Maybe it is coming to life like C5...

    Many thanks for all your friendly help.

    \Ö/

    Grrrr!!!

  20. To thank you all on this thread.

    Solved. Finally!

    As you know from the other posts I had to make an XP install CD from the installation on the C: drive. So I used the MS setup.exe on the C: drive to set up a copy on the indentical size D: partition (1st logical drive). I then booted to this partition and used the MS MUI rollback tool to remove the other languages.

    I then made a drive image of the D: drive with Image for Windows 1.64 and extracted the files from the image to a folder on the F: partition using TBI View (Two really good software tools from TeraByte Unlimited in Las Vegas) so that I could use nLite to cut it down to size and make an ISO.

    So I then formatted the D: partition (1st logical drive) and re-installed from the nLite ISO giving me XP Pro SP2 (OEM) without any unnecessary junk and practically no MUI. (Some keyboards did manage to get past this process but got picked out and deleted from the remaining MUI cache using Reg Organiser.)

    As the SP3 downloaded file turned out to have corrupt .cab files, according to the Avast AV, (Previous post) I downloaded the US SP3 ISO and burned it to CDR.

    I then re-installed and ran the subinactil.msi tool from MS and proceeded with the SP3 update which went in flawlessly.

    (Contrary to those who claim that SP2 has to be - fully - updated - before - SP3 will install.)

    I then added IE8 and all my other software archived on the F:partition, cleaned and optimised the registry, ran chkdsk, defragged the drive, and telephoned MS USA to validate the install.

    1 - click later, back up and running. :-)

    Just had to go online to update the AV, complete the validation, and add all the many security updates.

    Made a new drive image of the, fully functional, D: drive to archive and then 'restored' it to the C: drive.

    Re-booted to the C: drive edited the boot.ini file and formatted the ... 1st logical drive ... in the extended partition ... where the new install ... had been prepared.....

    Login - Logoff works perfectly, as all settings are US English, even with the Belgian (Period) keyboard. (There is a Belgian (Comma) keyboard, but they are quite rare.)

    I now have - NO - 'Teefer' (for NT) and 'wpsdrvnt' (Windows PS Driver NT) errors in the event viewer as there was no PS/2 keyboard and PS/2 mouse attatched when the initial installation was done and these legacy drivers no longer appear in the hardware device manager. Hooray!

    So - VERY MANY THANKS - to all of you on the Forum for your help, which has proved to be invaluable.

    Hope you - ALL - have a great day.

    Ian.

    PS

    Just - two - little things... See above.

    Now my primary partition shows as Local Drive D: (System with boot files) and the ... 1st logical drive ... shows as Documents C: ... \Ö/

    Checking the Event viewer reveals that MS, in its infinite wisdom, chose to re-assign the drive letters so that the 'system' (Big Brother) could keep track of things.

    Arrrggg !!! I feel like Winston Smith from 1984!

    Anyway, that is three up, one down, which has to be good and the entire system is much more responsive.

    'Apply' is very much quicker, for example.

    Also the registry is as new and very much smaller.

    Tonight I will see if it is possible to re-assign the drive letters using Boot-IT NG....

×
×
  • Create New...