There is a much higher potential for the binding of a Windoze app with the shell than other OS's. Alot of look'n'feel stuff, integration into drop-downs, default file associations, system tray entries and the like ad nauseum. The original idea of the registry was to replace the several *.ini files that were allowing Windoze to preserve state between reboots, but no doubt particularly blossomed when IE integration was attempted. I do have a couple of apps that do sit alone in some folder, keeping their own state information for persistent features, no doubt confined to using the standard core windowing etc OS features. At most one might manually create a shortcut, in the way one would for Windows 3.x - which was a GUI shell over a DOS version, clearly similiar to Linux's and their Desktops . The apps don't appear in the Control Panel's 'Add/Remove Programs' area, and don't have installers - typically unwrap from a zip into a user created directory and go from there. Eclipse is a notable example of this - you can have several versions ( Callisto, Ganymede ..... ) all separated neatly on the drive. Being Java based, the pre-requisite is a Java VM though.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Are the other OSes (Linux in various flavours and the Mac OS X) burdened with such a [registry] database (effectively)?
Certainly not in the same way!
In Linux at least, the functionality is more closely coupled to where the data is used...
General system configs are in the form of text files in "/etc". The desktops themselves keep whatever 'registry' data themselves in whatever format is useful to them. And then various persistent data is kept in "/var".
The only 'registry' that you'll find is the one as re-implemented in WINE!
No writing to the Registry, no shared .dlls, etc, and when the application was removed it was gone completely. No Registry pointers left, no unused .dlls, no problems with shared .dlls, nothing left to slow the system.
That reminds me of the particular silliness you get when a Windoze un-installer operates. Frequently it will attempt to remove *.dll's from system directories, but will ask you if you want to remove a particular dll as it may or not be shared with other apps. Granted that is an advantage of dll's to have commonality accessible across apps. But how can I decide whether to safely remove a dll [ presumably then as the last app 'clocking out' ] when I am not also given the information from the OS about it's sharing pattern? If I'm ignorant enough about an app to be using an uninstaller ( a likely base case ) then I'm also even MORE likely to be quite clueless about this or any other app's dll hooks. That suggests that the OS doesn't know either, hence the question. Not to mention the 'Yes To All' option on the dialog, which seems to suggest the scenario : that if I'm happy to erase one dll then I could also be happy to erase all other candidates for removal without being asked. This is despite the fact that whatever dll set we are examining for a thinning of the ranks is likely to have quite varied functionality contained within - thus needing different criteria to judge each instance within the set! Incongruous. Dll's aren't really an edge nowadays for memory management with the large and cheap PC level sticks, caches and whatnot. A product of the 640K days .....
No doubt about it, for every Windoze 'feature' a side industry has popped up with 3rd party gear to fix it! :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
It is always interesting to me when people who are generally very intellectually smart stoop to very immature comments about "the competition", e.g. pro-Linux / anti-Microsoft people who feel the urge to vent themselves in fanboy fashion by a perceived "cute" phonetic misspelling of the Windows operating system.
If you had valid arguments to use, they should stand on their merit alone. Childish behavior tends to suggest that there's a lot of growing up that needs to happen by those individuals before I put my trust in them that they are a good technical reference. Instead, I view them as blowhards, people who have become so pompous in their belief system that no amount of rational discussion is going to change their mind.
DLLs have a purpose. Versioning has a purpose. Yum / RPM / apt / Synaptic updates break things too. There are often a myriad of packages out there, and sometimes when you install packages to get one thing working in Linux, something in one of the perhaps multiple packages that were installed breaks functionality of something else.
Windows code was written by humans. Linux code was written by humans. Mistakes are made by humans. Ergo, Linux and Windows will have mistakes in it.
Oh chill out, Brian! We're just shooting the breeze! :-)
Read the thread closer - you'd note that I introduced the topic of troubles with Linux installs, pros and cons and whatnot - in a thread which began discussing much the same issues with app comparisons across OS's and CPU types. The thread title is stated as a query, and a waffly one at that.
But you're right, if anyone has mistaken what is said here for a good technical reference then let's bury that expectation quick slick! 'Caveat reader' or whatever.
I truly have always welcomed your contributions Brian, but why do you keep turning up when you surely don't seem to like it? You really can't expect to make these loosely disguised side-swipes at other contributors and have it pass by uncommented. The 'childish', 'blowhard', 'pompous', 'immature' and 'fanboy' stuff is in fact insulting and phrasing in a 'third person neutral pose' with 'No reply desired' doesn't excuse ..... :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
I truly have always welcomed your contributions Brian, but why do you keep turning up when you surely don't seem to like it? You really can't expect to make these loosely disguised side-swipes at other contributors and have it pass by uncommented. The 'childish', 'blowhard', 'pompous', 'immature' and 'fanboy' stuff is in fact insulting and phrasing in a 'third person neutral pose' with 'No reply desired' doesn't excuse ..... :-)
The fact is that discussion about pro vs. con can easily take place without all the over-the-top cutsy shenanigans. You do not know how many utterly incorrect things I have seen and/or heard in my time. Having used both OSes now, it makes it easier to spot "bollocks"... As I grow more familiar with Linux, the more I see that might be well and good for those who like minutea and precision control, just simply will not work for people who just want things to work out of the box.
My re-entry into the thread was because there was a bit of misinformation going about. All it took was a simple Google search to find the VDM software. I suppose I just have issues with things that come across as pure propaganda / FUD...
To borrow from "Zork"...
**********************************
FUD Control Dam #3
There is a tube of "Propaganda Exaggeration Cream" on the ground.
> read tube
Taken.
Introcuding "Propaganda Exaggeration Cream". Apply liberally to engage in obfuscation and blur the line between fact and fandom.
Unlike most distributions, Xubuntu locks the root (superuser) account and require users with administrative authorization to use sudo to execute many administrative functions that normally only the root user can do. This is a minor inconvenience to Linux guru and power user types, but is certainly more secure and safer for users new to UNIX and variants like Linux. The user account you made during the installation will have the required administrative powers to do this. The following procedures will require you to enter your password when the dialog pops up.
Not all of the BOINC projects have native 64-bit applications, so we need to add the 32-bit libraries required for these project applications. Open the package manager from the menu, Applications --> System --> Synaptic Package Manager and perform a search for the ia32-libs package. Mark this package for installation.
Now, we need the libstdc++5 package, for BOINC projects with applications that were compiled on the older C++ version 3 compiler. Perform a search for this package and mark it for install.
We also need two packages for BOINC... boinc-client and boinc-manager will be the version 5.10.45 applications. Find these two packages and mark them for installation.
I much prefer to avoid adding a few hundred MBytes of 32-bit libs onto 64-bit-only systems...
Any reason for no 64-bit compiled version of Einstein?
(It is only a compile flag after all, even if no additional optimisation is done...)
It's not that simple, the current E@H code contains manually crafted assembly code that needs some changes to support 32 bit and 64 bit flavors of the app. Actually the required changes are not that complex. However, I'm not convinced yet about the performance aspects, I think a native 64 bit app would be worth a try if it gave you a 10%+ performance increase (personal opinion) for AMD AND Intel, and under Linux I haven't been able to get there yet, even tho I have a feeling that it should be possible.
There is a much higher
)
There is a much higher potential for the binding of a Windoze app with the shell than other OS's. Alot of look'n'feel stuff, integration into drop-downs, default file associations, system tray entries and the like ad nauseum. The original idea of the registry was to replace the several *.ini files that were allowing Windoze to preserve state between reboots, but no doubt particularly blossomed when IE integration was attempted. I do have a couple of apps that do sit alone in some folder, keeping their own state information for persistent features, no doubt confined to using the standard core windowing etc OS features. At most one might manually create a shortcut, in the way one would for Windows 3.x - which was a GUI shell over a DOS version, clearly similiar to Linux's and their Desktops . The apps don't appear in the Control Panel's 'Add/Remove Programs' area, and don't have installers - typically unwrap from a zip into a user created directory and go from there. Eclipse is a notable example of this - you can have several versions ( Callisto, Ganymede ..... ) all separated neatly on the drive. Being Java based, the pre-requisite is a Java VM though.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
RE: Are the other OSes
)
Certainly not in the same way!
In Linux at least, the functionality is more closely coupled to where the data is used...
General system configs are in the form of text files in "/etc". The desktops themselves keep whatever 'registry' data themselves in whatever format is useful to them. And then various persistent data is kept in "/var".
The only 'registry' that you'll find is the one as re-implemented in WINE!
Cheers,
Martin
See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)
RE: No writing to the
)
That reminds me of the particular silliness you get when a Windoze un-installer operates. Frequently it will attempt to remove *.dll's from system directories, but will ask you if you want to remove a particular dll as it may or not be shared with other apps. Granted that is an advantage of dll's to have commonality accessible across apps. But how can I decide whether to safely remove a dll [ presumably then as the last app 'clocking out' ] when I am not also given the information from the OS about it's sharing pattern? If I'm ignorant enough about an app to be using an uninstaller ( a likely base case ) then I'm also even MORE likely to be quite clueless about this or any other app's dll hooks. That suggests that the OS doesn't know either, hence the question. Not to mention the 'Yes To All' option on the dialog, which seems to suggest the scenario : that if I'm happy to erase one dll then I could also be happy to erase all other candidates for removal without being asked. This is despite the fact that whatever dll set we are examining for a thinning of the ranks is likely to have quite varied functionality contained within - thus needing different criteria to judge each instance within the set! Incongruous. Dll's aren't really an edge nowadays for memory management with the large and cheap PC level sticks, caches and whatnot. A product of the 640K days .....
No doubt about it, for every Windoze 'feature' a side industry has popped up with 3rd party gear to fix it! :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
It is always interesting to
)
It is always interesting to me when people who are generally very intellectually smart stoop to very immature comments about "the competition", e.g. pro-Linux / anti-Microsoft people who feel the urge to vent themselves in fanboy fashion by a perceived "cute" phonetic misspelling of the Windows operating system.
If you had valid arguments to use, they should stand on their merit alone. Childish behavior tends to suggest that there's a lot of growing up that needs to happen by those individuals before I put my trust in them that they are a good technical reference. Instead, I view them as blowhards, people who have become so pompous in their belief system that no amount of rational discussion is going to change their mind.
DLLs have a purpose. Versioning has a purpose. Yum / RPM / apt / Synaptic updates break things too. There are often a myriad of packages out there, and sometimes when you install packages to get one thing working in Linux, something in one of the perhaps multiple packages that were installed breaks functionality of something else.
Windows code was written by humans. Linux code was written by humans. Mistakes are made by humans. Ergo, Linux and Windows will have mistakes in it.
No reply desired... Just contemplate...
Oh chill out, Brian! We're
)
Oh chill out, Brian! We're just shooting the breeze! :-)
Read the thread closer - you'd note that I introduced the topic of troubles with Linux installs, pros and cons and whatnot - in a thread which began discussing much the same issues with app comparisons across OS's and CPU types. The thread title is stated as a query, and a waffly one at that.
But you're right, if anyone has mistaken what is said here for a good technical reference then let's bury that expectation quick slick! 'Caveat reader' or whatever.
I truly have always welcomed your contributions Brian, but why do you keep turning up when you surely don't seem to like it? You really can't expect to make these loosely disguised side-swipes at other contributors and have it pass by uncommented. The 'childish', 'blowhard', 'pompous', 'immature' and 'fanboy' stuff is in fact insulting and phrasing in a 'third person neutral pose' with 'No reply desired' doesn't excuse ..... :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
RE: I truly have always
)
The fact is that discussion about pro vs. con can easily take place without all the over-the-top cutsy shenanigans. You do not know how many utterly incorrect things I have seen and/or heard in my time. Having used both OSes now, it makes it easier to spot "bollocks"... As I grow more familiar with Linux, the more I see that might be well and good for those who like minutea and precision control, just simply will not work for people who just want things to work out of the box.
My re-entry into the thread was because there was a bit of misinformation going about. All it took was a simple Google search to find the VDM software. I suppose I just have issues with things that come across as pure propaganda / FUD...
To borrow from "Zork"...
**********************************
FUD Control Dam #3
There is a tube of "Propaganda Exaggeration Cream" on the ground.
> read tube
Taken.
Introcuding "Propaganda Exaggeration Cream". Apply liberally to engage in obfuscation and blur the line between fact and fandom.
***********************************
Take the polite hint
)
Take the polite hint Brian.
Change tack, or be moderated without further notice.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
RE: does anyone know how
)
I'm on the winXP 32b box right now with a E@H running and task manager shows it staying well under 90MB
Couldn't resist the shameless plug below for the team board... and now back the thread.
http://dcteam.guru-mountain.com/howto/xubuntu03.html
Bottom of 3rd page in the how-to talks about this and the libstdc++ you may also need for some projects (for some reason I'm thinking CPDN here).
RE: Good news, the
)
I much prefer to avoid adding a few hundred MBytes of 32-bit libs onto 64-bit-only systems...
Any reason for no 64-bit compiled version of Einstein?
(It is only a compile flag after all, even if no additional optimisation is done...)
Happy crunchin',
Martin
See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)
RE: I much prefer to avoid
)
It's not that simple, the current E@H code contains manually crafted assembly code that needs some changes to support 32 bit and 64 bit flavors of the app. Actually the required changes are not that complex. However, I'm not convinced yet about the performance aspects, I think a native 64 bit app would be worth a try if it gave you a 10%+ performance increase (personal opinion) for AMD AND Intel, and under Linux I haven't been able to get there yet, even tho I have a feeling that it should be possible.
CU
Bikeman