Again XP really slow opening interbase database and crashi..

[mrt]

Ran fine on xp sp1 and win2k sp4

What dll's were radically changed by MS between theses OS issues. How
do I find out?

[shenan stanley]

MrT wrote:
> Ran fine on xp sp1 and win2k sp4
>
> What dll's were radically changed by MS between theses OS issues.
> How do I find out?

Have you contacted those who support Interbase/Crytsal Reports and verified
you are using a compatible version/updated version of their software?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

[mrt]

Shenan Stanley wrote:
> MrT wrote:
>> Ran fine on xp sp1 and win2k sp4
>>
>> What dll's were radically changed by MS between theses OS issues.
>> How do I find out?
>
> Have you contacted those who support Interbase/Crytsal Reports and verified
> you are using a compatible version/updated version of their software?
>

Hi:

Thanks.

It was running fine on 2k SP4 and XP sp1. Are you implying that MS
issues SP/updates that can compromise existing apps?

[shenan stanley]

MrT wrote:
> It was running fine on 2k SP4 and XP sp1. Are you implying that MS
> issues SP/updates that can compromise existing apps?

I'm saying that Microsoft does not support the third party applications you
choose to run - thus their patches may change something a third party
application you use has chosen to utilize for its own purposes.

If you purchase a vehicle and get an after-market part for it and later - a
recall on the car (something has been deemed dangerous in some way) changes
the part your after-market part fits on in such a way that the after-market
part no longer fits... Well - it's not the original manufacturer's
responsibility to make your after-market part fit (nor will the after-market
part manufacturer do much but offer to sell you a new after-market part that
does the same thing except fits the new situation.)

Your third party applications, your hardware, etc - all of those things are
supported by the manufacturers. Microsoft makes and patches their part of
the equation and they cannot (think of the millions of applications and the
millions of versions on top of that for the many different OSes out there)
make sure someone else has not linked into some component they are changing
to make the OS run better, faster, more secure, etc.

An application is written for a specific OS and sometimes a specific Service
Pack (when speaking of Windows OSes.) Check out the packaging of the
applications in the stores someday... "Requirements: Windows XP SP3 or
greater" and the likes.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

[mrt]

Shenan Stanley wrote:
> MrT wrote:
>> It was running fine on 2k SP4 and XP sp1. Are you implying that MS
>> issues SP/updates that can compromise existing apps?
>
> I'm saying that Microsoft does not support the third party applications you
> choose to run - thus their patches may change something a third party
> application you use has chosen to utilize for its own purposes.
>
> If you purchase a vehicle and get an after-market part for it and later - a
> recall on the car (something has been deemed dangerous in some way) changes
> the part your after-market part fits on in such a way that the after-market
> part no longer fits... Well - it's not the original manufacturer's
> responsibility to make your after-market part fit (nor will the after-market
> part manufacturer do much but offer to sell you a new after-market part that
> does the same thing except fits the new situation.)
>
> Your third party applications, your hardware, etc - all of those things are
> supported by the manufacturers. Microsoft makes and patches their part of
> the equation and they cannot (think of the millions of applications and the
> millions of versions on top of that for the many different OSes out there)
> make sure someone else has not linked into some component they are changing
> to make the OS run better, faster, more secure, etc.
>
> An application is written for a specific OS and sometimes a specific Service
> Pack (when speaking of Windows OSes.) Check out the packaging of the
> applications in the stores someday... "Requirements: Windows XP SP3 or
> greater" and the likes.


Thanks. Understand. I did a compare between older (win2k sp 4) and newer
xp (sp2) dll's. Fo the newer version in xp I will put the old dll in the
local directory where the app is located so it will find those first.
Worth a try.

[mrt]

db wrote:
> sometimes there are programs
> that need to be reinstalled or
> updated when the o.s. is updated.
>
> not all programs are engineered
> that way but yours could be.
>
> but it seems that the makers of
> crystal reports or the program
> that has it as an add-in/module,
> should have a solution,
>
> since it is likely that they incurred
> the same problem like yours.
>
> incidentally, try a clean booting
> normal mode and see if it helps
> any with the performance of
> windows and your database.
>

What is clean booting normal mode??? Isn't that the normal boot???

[mrt]

Speed problem solved by setting affinity on ibserver using imagecfg.exe.
Problem with the dual core. Hopefully it will solve problem on deployed
machine with HT.

Thanks.

Best regards


db wrote:
> a clean boot is a method
> to disable automatic programs
> from starting with windows.
>
> sometimes it is the automatic
> programs/startups that are loaded
> into memory and inhibit
> windows performance.
>
> it is not all that different from
> booting into safe mode because
> the automatic programs are
> disabled for safe mode operations.
>
> that is why if windows performs
> better in safe mode but not as
> well in normal mode,
>
> then the problem could be attributed
> to the automatic programs/startups.
>
> ------------------
>
> if you want to initiate a clean boot
> here are the steps that can be done
> while in either normal mode or
> safe mode.
>
> click on start>run>msconfig
>
> after you type and run msconfig
> a window will pop up.
>
> then under the startup tab you
> will find those programs that
> automatically start with windows.
>
> you can uncheck them and they
> will become disabled, then click
> apply.
>
> you may want to jot down which
> ones you disabled, just for future
> reference.
>
> afterwards go to the services tab
> and "hide" all microsoft services.
>
> then what remains can be disabled
> as well.
>
> click apply and reboot into normal
> mode.
>
> what should occur is that windows
> will launch without those third
> party programs and services.
>
> if you find that windows works
> better than before, then you successfully
> disabled the problem.
>
> the next thing you should do is
> to figure out what exactly should
> be started automatically with windows.
>
> my suggestion is to only have one
> anti virus program automatically
> startup with windows.
>
> let us know what you discover.
>
> -------------
>
> incidentally, go ahead a make
> a system restore point for today
> and before you make changes to
> the msconfig.
>
> that way you can easily revert back
> windows to a former state, if you
> choose to.