FS Autostart or Cacheman in FSX???

[NicksFXHouse]

I also performed the defrag and registry operations in Windows Safe Mode.

Rob

I am indeed glad your experience with the process produced a successful outcome and it sounds like you were prepared as anyone should be in the event of a problem, however, I must ask why the O&O maintenance software was run in safe mode. As far as I am aware O&O does not specify safe mode should be used and O&O must have access to services which I am not sure are properly enabled and fully functional under safe mode conditions. I am just curious.

About the registry issue,...
Did you attempt to run the registry compact in Windows under normal boot conditions with the same results?

I assume you disabled the registry monitor in the RM software as I specified?

Were there any other AV or monitor programs running while this was happening?

I assume you have a good professional AV installed such as NOD32 and system scans have not turned up any critters in the wings?

I am not a software engineer however the only way I can fathom a halt like that is if the registry was being monitored or accessed from another software source and it prevented completion and a proper rewrite of the defragmented registry files at the end of the run. The same way Windows will refuse to allow a folder to be deleted, moved or renamed even if one file in that folder is simply being accessed for a properties check. Assuming you did attempt to run RM in full mode with the same results, it sounds like something else in the system has the registry in a state of constant read/write access and/or something prevented RM from completing the final write in its task.


In Windows XP SP2 there is a feature called Data Execution Prevention in which the default setting is "only for critical Windows programs and services"

I have never seen a DEP issue on my own personal systems nor have I seen any mission critical office system I have run RM on be affected by DEP however it is quite possible DEP on some systems is somehow enabled for more than just critical Windows programs and services even though the Windows setting specifies otherwise and is forcing the software to fail mid-stream where the failure allows the old registry to be deleted by RM command and the new one to -not- be written when RM attempts to execute the final phase.

There are some boot.ini files that can have DEP commands written to the boot line which would direct the Windows settings. The command

[robmw]

Nick,

I've just reread what I said about running in Safe Mode and I'm kicking myself for not proof reading my posts carefully enough  :-[. What I should have said was that I ran RM in Safe Mode, on advice from the vendor in response to my compaction problem. You are quite right about O&O as this won't run in Safe Mode because the agent service can't be started. Sorry to unintentionally mislead you and anyone else who read my post...

So regarding the registry issue, yes, I did try this the first time after a full boot which was when I first noticed the problem. RM monitoring was disabled, as was my AV and firewall (NOD32 and Outpost).

My DEP setting in boot.ini is the recommended one which I vaguely remember amending after installing SP2 on advice from the AV or firewall vendor... I may well try your suggestion of using the AlwaysOff option at some point but want to get on with some flying first  :).

It's quite possible there are some quirks in my system as I haven't reinstalled in 3 years and have swapped a number of different configurations and software packages in that time. In fact I'm quite surprised that my system is still very stable after all this time. Having said that my PC is used only by me and I do take regular full system backups and keep additional backups of all my data and purchased software etc. etc. so I'm not afraid of trying new things. I'd thoroughly recommend partition backup software in particular as this let me restore my system in very short time (20 mins).

[NicksFXHouse]

[quote]Nick,

I've just reread what I said about running in Safe Mode and I'm kicking myself for not proof reading my posts carefully enough

[NicksFXHouse]

Here is how I go about installing a system if anyone is interested:

NOTE: YOU DO IT, YOU BOUGHT IT

[NicksFXHouse]

IMPORTANT NOTE ABOUT WINDOWS XP SP2
If your Windows Installation CD does not come with SP2 and you must updated from the web, MAKE SURE YOU REBOOT TWICE AFTER SP2 IS INSTALLED before going back to Windows update to continue the update process. You can also download the SP2 update separate from the Microsoft Download Centre. The important thing to remember is give the system time after it installs (wait before rebooting) and also give the system time once the system has rebooted. (wait 2-5 minutes before doing anything) and then REBOOT AGAIN.

[DizZa]

NOD32 had a tendancy to end services.exe when I logged in to my computer, this would cause my PC to restart.

If anyone else has this problem, quickly create a new user on your computer, run NOD32 in that. Disable all NOD32 protection THEN uninstall it. Do not uninstall NOD32 before protection is disabled as this may result in your internet access being cut off. Not something you want to do.

[robmw]

Ahhhh! Ok, that makes more sense about O&O. I thought I was going senile in my old age.  ;D

Thanks for your continuing interest Nick - you really are putting some time into this!

As for RM, apparently they may be aware of something. I just found this on their support site:

I came across this info on the RM site after responding to you yesterday and with a bit more time on my hands earlier today I tried again using both your and the vendors suggestions. Still no luck though! Looks like there is something unusual on my system which is annoying but something I can live with. My registry actually isn't very badly fragmented at 7%, not too far from your recommendation.

Interesting about the layout of my partitions and makes perfect sense when I think about it. I can see that I am losing performance with my partition layout and I may consider changing this at some point, although as I use the PC for lots of other things it's not an easy decision to make! In any case this is very useful to know when I eventually migrate to a new machine sometime next year. Fortunately, I'm already running my photo sceneries and most of my other scenery on a separate physical disk to the OS and FS9.

Another lesson I'm taking from this is that for absolutely best results you need to apply these rules starting from scratch with a bare machine. So needless to say I'll be keeping all this information for the next time I build a system!

[NicksFXHouse]

[quote][quote]Ahhhh! Ok, that makes more sense about O&O. I thought I was going senile in my old age.

[NicksFXHouse]

NOD32 had a tendancy to end services.exe when I logged in to my computer, this would cause my PC to restart.

If anyone else has this problem, quickly create a new user on your computer, run NOD32 in that. Disable all NOD32 protection THEN uninstall it. Do not uninstall NOD32 before protection is disabled as this may result in your internet access being cut off. Not something you want to do.

Just like any other software product that may display abnormal behavior, like RM did for Rob, NOD32 is reacting to something specific in your system DizZa. It uses a /WAITSERVICE switch at boot designed to allow the system to start prior to its GUI interfacing and enabling the scanner however there are a number of possible reasons for the issue you are speaking of.

You may want to stop by this forum http://www.wilderssecurity.com/forumdisplay.php?f=15 and either search or post the issue. The folks there are very helpful and can typically nail a problem like that very quickly.

I would spend the time and research it out because that program is probably the best defense a system can have installed and unlike other packages it does not crush resources. I fly with it enabled and never had any problems.

[NicksFXHouse]

One last warning I wish to make quite clear

[NicksFXHouse]

Another tweak posted on the net that is not quite as bad but can be just as dangerous in some systems and must still be considered carefully is the use of:

NtfsDisableLastAccessUpdate= (from 0 to 1)

If you use Perfect Disk or any other defrag software which applies the

[Y]

Is there any way of moving the MFT area. After defragmenting my drive where FSX is, with O & O defrag, the yellow MFT area is still unmoved in the middle of the disk in the green processed area, can it be moved to the beginning or end of the disk?

If it cannot be moved does it matter too much?

Regards

Steve

[Splat762]

Totally off subject, but I'm just surprised my little post has grown to where it's at now.  ;D

Sorry....carry on gents.  ;)

[NicksFXHouse]

Is there any way of moving the MFT area. After defragmenting my drive where FSX is, with O & O defrag, the yellow MFT area is still unmoved in the middle of the disk in the green processed area, can it be moved to the beginning or end of the disk?

If it cannot be moved does it matter too much?

Regards

Steve

I do move the MFT when it is positioned close to the beginning of the drive and/or it takes up a great deal of space as the example graphic below demonstrates because the head of the drive must seek across that area. I prefer it be located at the end of the data area. It is not CRITICAL but I do move it because I like my RAID disk in perfect order. Solid State drives do not matter but with mechanical drives the least amount of seek the head makes, the better.







There is a way to do that however it comes with risks. When ever you use a partiton program which accesses the system at the lowest levels you run the risk of corrupting a boot. In the many times I have performed the operation I am bout to explain, I had it happen to me once with Partition Magic several years ago however I keep a backup for instant restore.

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


If you do not understand what I am saying below, do NOT attempt this. It will work and I have done it many times however it can come with risks.


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



The MFT will automatically be moved by Windows as a disk fills however there are 3 circumstances that will force the MFT to remain in place.

1.
The amount of data on the disk has not reached the threshold where Windows decides to resize the MFT area.

2.
The amount of data on the disk exceeds the space that would allow the MFT to be moved.

3.
Windows has never found any disk cluster errors during a CHKDSK /R operation and as such has not edited the file allocation table which will usually change the MFT zone position and size.

There is a way to turn off the MFT (set it to zero) in the registry however that does not always wipe out the area being allocated because that information is written to the file allocation table. Until that table is re-written or edited by Windows, the allocated space will usually remain untouchable.

It is possible to force Windows to wipe out the MFT and rewrite a new zone to the disk clearing the area and allowing the defrag software to optimize by moving files closer to the beginning of the disk.

a.
Using the software Partition Magic, reduce the primary partition by about 5 gigs.

b.
In the same operation instruct Partition Magic to create a new partition and the END of the first one (make it a primary partition and make sure the cluster size is 4k) using the 5 gigs of unallocated free space you just created.

c.
In the same operation have Partition Magic merge the new partition back into the primary partition (make X a folder on C named TEMP)

d.
Execute the operations. It will ask for a reboot and perform the operations in a Windows protected boot.

Once complete the system will reboot back into Windows. The file allocation table will be rewritten and you will usually find the MFT zone (reduced in size after the first reboot) located at the end of the disk, or away from the data area.

FIRST:
The TEMP folder you made requires a special method to delete it because it will have system files from the partition that was created in it. They are no longer being used but the system will lock the folder from being deleted none the less.

Open the TEMP folder (assuming Windows hidden files and folders is DISABLED) you should see a folder named: System Volume Information. Right click that, select Properties and the the SHARING tab. Under Network Sharing and Security, put a check in both boxes and click YES AND OK.. you will get a warning that the operation can not be done

[NicksFXHouse]

[quote]Totally off subject, but I'm just surprised my little post has grown to where it's at now.