Recommended Posts

Ive found the mod thats causing the 13 error messages.

However, its not a problem with the mod itself, its actually conflicting with another mod.

Im using a search algorithm i learnt in college and have so far narrowed down the search for the conflicting mod to 6 possibles.

btw, just so everyone knows how much dedication im putting into this, and so they understand why its taking so long...

- im a perfectionist, so when i start something, i do the best job i can before i finish it.

- ive made a large database of m$ 2K updates and related info, covering over 100 updates.

- ive manually installed every single one of around 120 setup files, one at a time, with a reboot after most, when gathering ETA and reg detection data.

- i have used AP to install every single update one at a time, with reboots after most of them, while bug fixing.

- and if you add up all the reboots and reformats ive done on my test machine, it must add up to at least 200.

:D

585983703[/snapback]

Sooooo......you saying it's ready now? ;)

*taps foot impatiently*

The scary part is that Blaze is not kidding... He actually got all ETAs based on the real thing, not just an estimate!!!

That's all fine and good, but what if someone is using it on a system that is much slower than the one Blaze is testing on? Are you checking processor speed and total memory to determine some sort of multiplying factor for the ETAs you have recorded? (Please tell me no, I advise you to seek professional help if you're going that far with it :p)

^ The answer is, indeed, no. But only because cpu speed and memory are not always the key factor. Besides, AutoPatcher v5 only allows one ETA value. If you disable backups, things will go much faster. I usually go with 'safe' values (i.e if an installation takes 20 seconds on my pc, i put 40), so people see AutoPatcher report "2 hours etc etc". When they go ahead and install, it usually takes a little less than an hour. I think blaze is doing a great job, giving us a better estimate on how long an installation will take. ETAs are, by nature, never 100% accurate, that's why we call them "estimates". With Blaze's work however, I see those estimates becoming more accurate, and with AutoPatcher Version 6.0 (which will allow separate ETAs for installation with and without backups), things should get even better.

^ Yeah, but optional work ;) See, AutoPatcher 6.0 will be smart when it comes to .amc handling. All properties used by the .amc are loaded, and then AutoPatcher fetches the needed property. This way, you can use as many properties are you like. If you forget to add the ETAWithNoBackups property, AutoPatcher will use the ETAWithBackups property :) If you put the Description property in before the Name property, there will be no problem :) AutoPatcher will find the right one :D

Hey Blaze,

Just wondering what the current status is.? Do you think the release will come before the end of this week?:huh:: *crosses fingers*

585999664[/snapback]

im gonna have to say no.:((

this last error is getting extremely complicated to work out.

its taking a hell of a lot of tests to work out exactly whats conflicting, and each test takes about 2 hours to complete.

for every test i have to reformat, reinstall windows, copy the AP 2K cd to the hard drive (a lot faster to run off than the cd), load AP, make the selection for the next test, and wait through the installation to get the result, then repeat for the next test.

im getting though about 3 or 4 tests a day, but its seriously draining my energy.

and its not as simple as a problem with a single module, or one mod conflicting with another.

There are multiple combinations of modules that can cause the error!!!

The first combines at least 4 modules, the fourth of which i havent worked out yet!!

im still in the middle of a long process of working out the conflicts before i can even begin working out why.

only then can i start to work out a solution, try it, and if successful, move on to the packing stage.

im affraid it may take at least another week:((

and dont get me wrong, this has nothing to do with me being picky, i seriously cant release it in the state its in with this error. its become a major problem.

for every test i have to reformat, reinstall windows, copy the AP 2K cd to the hard drive (a lot faster to run off than the cd), load AP, make the selection for the next test, and wait through the installation to get the result, then repeat for the next test.

Wait wait wait... you're telling me that you're not using something like Norton Ghost to speed this process up? If you had a ghosted backup of the drive before you started testing then you would reduce the total time for each test by about 45 minutes (or however long it takes to format the drive and reinstall 2000)!! The latest version, 9.0, can even be purchased and downloaded from Nortons site for only like $50 USD. It will save you a bundle of time, trust me.

Agreed. Use a drive imaging tool.

To speed it up, you can even partition the HD. set 5 GB to the system. The rest to data.

And only use the partition function of the drive image tool - I use Ghost.

When you image a partition, you can save it to another partition on the same physical disc. Takes about 20-30 min depending on the compression, can restore in 15 minutes depending on the info. Even less if its a pure system.

I use this to backup the system of my laptop all the time, while keeping all my data.

As I use symbolic links I can even back up profiles, email etc, that normally is required by the system to be on c drive.

The current version of Autopatcher is stored on the data drive - no need to reload AP.

for every test i have to reformat, reinstall windows, copy the AP 2K cd to the hard drive (a lot faster to run off than the cd), load AP, make the selection for the next test, and wait through the installation to get the result, then repeat for the next test.

586000315[/snapback]

Why not to use a Virtual Image like Virtual PC or vmware?

This way you can save the image file on the stage you need, make every test and restore the imagem file when you need to start over again.

It will be even faster if you backup the image on the HD.

___

RP

ok, ive got hold of a copy of vmware.

ive got it setup and have created a snapshot.

hopefully this'll save some time, however i redid the first test to check the vm software acted the same, but i think it had a different result.

ill do a re-test after gathering the results i need.

Agreed.  Use a drive imaging tool. 

To speed it up, you can even partition the HD.  set 5 GB to the system.  The rest to data. 

And only use the partition function of the drive image tool - I use Ghost.

586003040[/snapback]

btw, the test comp's only got a 4gig hdd :)

Edited by TheBlazingAngel

VMWare will run slower than an actual system, as 2 systems are running.

With Ghost images, you can use high compression to keep the size down. Not sure on actual figures, but I think its close to 50% depending on content. I have 4GB on my system part at the moment. Not sure if was that when I imaged it, but turn off system restore, hibernation, and move the page file to another partition, and you will save a lot of space. no point using sys restore if your going to re-image it anyway. My image is just slightly over 2GB. Thats with office, photoshop, dreamweaver and all the others installed. a pure system, you should be able to fit on a 2/2 split.

Or better yet, scrounge up several 4GB HDs and image them all first. Then you can just keep swapping hard drives out as you test. While you got one test running you can have the last hard drive being reimaged. This is assuming that you have all that spare hardware lying around. I do :p

Can I suggest you delay this until Microsoft Releases the the update rollup for windows 2000. Seeing as this is to be the final update released for windows 2000. And expected to be released before the end of this month..

My understanding, it could install as a single module, and would probably have the conflicts you are finding pre-fixed.

I hope you didn't do all that work for nothing blaze :unsure: ... The update rollup is not the last update for 2000. After the end of this month, Microsoft will only be releasing security related updates for 2000, so this isn't the one end-all patch. Basically in the Windows 2000 lifecycle it is coming to the end of the "Mainstream Support Phase" and entering the "Extended Support Phase". From Microsoft:

Extended support includes:

* Paid support

* Security update support at no additional cost

* Non-security related hotfix support requires a separate Extended Hotfix Support contract to be purchased. Per-fix fees also apply.

* Microsoft will not accept requests for warranty support, design changes, or new features during the Extended support phase.

* Extended support is not available for Consumer, Hardware, Multimedia, and Business Solutions.

This update rollup will probably contain updates from around 50 of the modules that Blaze has already made. From the articles I'm reading, Microsoft already has completed testing on it and it is ready to go. Release will probably come in the next week or two. Something to keep in mind blaze :o

damn it...i knew it was coming sometime but not so close to getting this completed.

months and months of work for nothing... :(

dont worry though, ill keep up the work until i fix the errors or the update rollup is released and then ill see what happens.

Ive kinda given up for now. im waiting for tuesday to see if this big rollup is comming out.

if it does ill quickly add it and remove any that it replaces, and if the errors gone ill have it out in no time. but if not i guess its back to work.

In Microsoft's anouncement I've sow that they will release that rollup update somewhere in the middle of this year, do you have some new information on this or how/from where do you know this will be released tuesday? Or what tuesday? :) :whistle:

586062348[/snapback]

The update rollup for W2K SP4 will definitely be out before the end of this month. Looks like the rollup will miss the official "Patch Tuesday" for this month (today), but I imagine we'll see it next week or the week after. We're pretty sure it will be on a Tuesday because Microsoft always releases patches on a Tuesday.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.