11 Aug
2004
11 Aug
'04
4:36 p.m.
I just ran the same image under Win XP. Instead of hanging the image,
it pegged the CPU at 99%.
Nevin
Nevin Pratt wrote:
OK, I had time to look at this again.
There is only one storage process-- the SWImageStorage
It looks like SWImageStorage does not attempt an image save unless it
detects that the swiki changed. But, if it attempts to save the
image, the image is hosed, and the resulting image is also hosed.
The problem is definitely still there.
Nevin
chris(a)chrisburkert.de wrote:
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
Hi Nevin,
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
I "upgraded" yesterday. The problem is
still there. The image hung
over the evening.
could you please take a look in you process browser and make sure that
there is only one storage process?!? The best is to kill all and create a
new one.
I'm using Squeak 3.6 final, on FreeBSD. The
latest version of SmallWiki
on SqueakMap is 0.9.23-- this actually seems to be a "backrev" from the
one I started with last fall:
(on the "new" image) SWSmallWiki versionString --> 'SmallWiki
0.9.23'
(on the "old" image) SWSmallWiki versionString --> 'SmallWiki
1.0'
I changed this version string which came from the VW version, because it
was not the correct string. You the versioning numbers from SM. Currently
it should be 0.9.23-6 for the kernel which means it is revision 6 of
0.9.23.
For what its worth, when the install asks if I
want the Star Browser, or
any of the other extras, I say "no".
You don't have to load these packages. So "no" and "yes" are
correct answers.
Chris Burkert
PS: I'm away for 2 weeks so please don't expect answers for this time. I'm
cycling from the ore mountains in saxony to wallis in switzerland and
back. Till then ...