Quote:
|
Originally Posted by arpsh
That's exactly what I tried on my 1000 but no joy - I think we can safely say that the 1000s don't support snap extensions (unless of course anyone out there knows different).
|
There is a usenet posting on google about this - someone has done it.
Look for msg-id <3efed8ef$0$30820$afc38c87@news.optusnet.com.au>
All credit to the original poster Robert Lowery.
In case you can't find the articles I'll briefly quote from it:
"The trick to get it working was to use the hidden webpage
http://servername/config/debug
I changed the hardware version number using the command "bios
PlatformBytes 4 0 0". My Snap 1000 was version 3.1.1, the 4.0.0 was just a guess.
This change allowed the update to succeed (I used the OSUpdate.exe
utility, but I imagine using the Web Page or Assist will also work). I then reset
my hardware version back to 3.1.1 just to be safe.
I then enabled the JVM (you can use either the webpage or "jvm engine
enable" in the debug webpage, but it failed to start.
I tracked the problem down using "info log T" in the debug webpage and
found that the jvm was failing to get enough memory. By default the JVM was
trying to get 24MB and my Snap 1000 has 32MB total. I changed this down
to 8MB using "jvm ram 8", and while I was at it enabled ssl with "jvm ssl
on".
After reboot, my snap server now supports SSL connections (albeit slowly)."
A second posting notes a caution:
"I just tried this again after mucking up my Java$ network share, but this
time I forgot to reset my hardware version number to 3.1.1 before the snap
server rebooted, and I think I have turned my snap server into a boat
anchor, as it no longer boots. Looks like I'll have to remove the bios
and reprogram it back to 3.1.1
So in summary, the instructions in my previous posting work perfectly,
just reset the hardware version back as soon as snap_jvm.sup starts installing."
This thread is really useful - I've already upgraded a couple of Snapservers after coming across it.
phaedrus