So you say they should start all over again with 32bits and then 64bits?nooby wrote:Guys, hope you can bear with a naive noob.
All this trouble with 64Bit???
Would it be very demanding to make a 32-bit version
and then you would have plenty of time to get the 64 bit
version totally or absolutely compatible with all drivers
and such complications?
Having a multiuser Puppy that just works is a sensation.
So why add the complexity of 64-bit compatibility from Scratch?
I "vote for" to have both 32-bit and 64-bit and most being used to
32-bit do look for that and the enthusiasts have the patience to
wait for the 64-bit to come a bit later? Only my ignorant rant.
Edit
Here is one reason I don't like SeaMonkey. AutoUpdate
and it remember too much even when one tells it to delete history.
Read here
http://www.murga-linux.com/puppy/viewto ... 331#635331
Quote/
For some years now I've had Seamonkey set to delete browsing history when shutting down, as well as most other residues of online activity.
So I was dumbfounded when I happened to open the tab:
Tools/Data Manager
to see a list of domains that seems to include most, if not all, of the sites I've visited over the past several years!
At the bottom of the page I see a "remove" tab, but it's greyed out.
What use is clearing your history if every domain you've visited is shown and can't be removed?
Do other browsers have this same function?
/unquote
I'm switching to Fatdog because it's 64bits. There are already lots of puppy 32bits. You could use fatslacko...
And correct me if i'm wrong, but wouldn't be better if it's written from scratch from 64bits rather than make a 32bit version and then convert it to 64bits?
Btw, the project is already on beta1...