|
|
Post by Kevin McAleavey on Mar 6, 2012 3:44:16 GMT -5
In this build, we've added groundwork for support of OpenVPN although in this build, it has to be manually started. If anyone wants to try OpenVPN, contact support and I'll be happy to tell you how to fire it up. OpenVPN's client, when started will open an empty window for you - you have to access the icon on the top right in order to configure it, but we don't know for sure if OpenVPN's kernel component will start automatically or not since we don't use OpenVPN here, nor did any of our in-house alpha testers.
Broadcom cards from Dell, Apple and other manufacturers are now supported, we're hoping that we have them all now. In order to support Broadcom with zero cooperation from Broadcom, we've provided this support using Broadcom's Microsoft driver for BCMWL5 which should cover just about all of their recent cards. If you have any issues with Broadcom wifi, we will need for you to email us diagnostics since we have a BWI and BWN Broadcom driver of our own and so won't be able to figure out the cause of any issues without seeing diagnostics.
We've hopefully solved the boot issues with new code from BSD as well as "idiot-proofing" both our knos2usb as well as our new "upgrade" module which will allow you to automatically upgrade from KNOS 9 beta without risking the loss of data on drives or sticks which are large enough to contain a "personal" data area.
Other small improvements including the final BSD9 kernel pieces are included in here, so we hope this will go smoothly and will allow us to do our actual release of KNOS 9 soon.
|
|
|
|
Post by pharrisire on Mar 6, 2012 14:45:04 GMT -5
Got the email to download, and got both 32 and 64 bit, but none of the
CRC32, MD5, or SHA-1 matched your email's.
And the size matched the previous downloads, so it looks like
the older version is still there instead of the new.
|
|
|
|
Post by Nancy McAleavey on Mar 6, 2012 21:04:44 GMT -5
My apologies. The links were in error,and an email correcting those links has been sent. The CRC,MD5 and SHA-1 stats are correct for the RC files. Once again, sorry for any difficulties this posed.
|
|
|
|
Post by jerry on Mar 9, 2012 15:24:56 GMT -5
I downloaded the 32 bit and the SHA-1 and MD5 hashes match but the CRC32 hash doesn't for the unpacked KNOS9-RC. Hashtab reports the CRC32 hash is 472C3404 and the link via your email has the CRC32 hash as 97368E52 Thanks for help with this. Waiting to burn  |
|
|
|
Post by jerry on Mar 9, 2012 21:36:13 GMT -5
Downloaded again and get the same hash of 472C3404  |
|
|
|
Post by Kevin McAleavey on Mar 10, 2012 5:23:55 GMT -5
Downloaded again and get the same hash of 472C3404 Cool ... this one's easy! I suspect Hashtab is pulling that CRC32 on the "size on disk" rather than the actual original file size that might be smaller than the cluster size of the hard disk when it's unpacked which might have caused Hashtab to calculate it incorrectly. When a file is smaller than a cluster on that last cluster, Windows will fill the space to equal the cluster size itself, leaving what is called "slack space" behind where the file segment left over is smaller than the cluster. We use Hashtab 2.3.0 on this end to calculate those on an old XP SP3 machine (we haven't used Windows here in years now other than to pack those files to ensure they're happy on Windows, and that machine hasn't seen the intarwebs since 2009). If the SHA-1 and MD5's are correct though, your file is good. Both of these hash methods are far more sophisticated than the old CRC32 method and we build with authenticity verification plus a recovery record when we pack those, so if there were any error or corruption, UNRAR would spot same and complain about it. Given the size of the file, we wanted folks to have every possible chance to win. So I'd have to say go ahead and burn it and ignore the CRC32. If it unpacked quietly, then it's good. My bet is that it's seeing the end of file marker and that's the cause. KNOS is Unix-based and that's different from Windows. KNOS is built by a KNOS machine. The RAR is built on a Windows machine. SHA and MD5 only measure the data itself. I'm actually feeling kinda inclined to lose the CRC32 values in the distribution if they're capable of being inaccurate and causing concern since SHA-1 or better is the best way to assure accuracy. The longer hashes are FAR more accurate in detecting corruption or tampering. Alas, the version of hashtab we're using doesn't do SHA-256 which is even better. If you've got the RC release ISO at the end of it all rather than "beta" without warnings from the UNRAR, then all's well with the world, it'll work. |
|
|
|
Post by jerry on Mar 10, 2012 8:12:47 GMT -5
Greetings Kevin, I'm wondering if the change to the CRC32 is due to some corruption upon upload? I burned to two separate DVD+RW discs. Initially, the disc wouldn't complete the burn due to errors. I switched discs and it completed the burn but wouldn't complete verification without errors. I tried to boot up and got the 0x04 error after boot loader found. Back to windows and I erased the data on DVD, then I burned KNOS again and the verification of data completed as well. Thought it would boot this type but nope..got same error message upon boot up..see pic... Attachments:
|
|
|
|
Post by jerry on Mar 10, 2012 18:53:18 GMT -5
Well..I used another burning program and it worked(Was using Nero and Ultra Iso worked). So I'm currently posting from KNOS 9 RC. What I've discovered thus far..you have to bounce around some on youtube to get flash functioning with FireFox. I don't see the clear flash cache icon any longer but once flash started working, I didn't have any problems.The epiphany browser wouldn't play youtube videos at all. The little loading circle just spun w/o progress. Chromium browser wouldn't load. The little KNOS clock spun and then disappeared and the mouse arrow returned. Tried to load the browser 3 times unsuccessfully. I still don't have any sound for the SoundBlaster Live card from Dell. We've covered that before and I don't expect to get sound since the drivers aren't available. How do you install a printer? Manage printer from applications wouldn't work and manage cups wanted a password. So that's what I've discovered thus far. One final thing: I'm running this on an old 2003 Dell running XP SP3 with one gig of RAM on a Pentium IV. Took awhile to boot from the DVD but expected that. |
|
|
|
Post by Kevin McAleavey on Mar 10, 2012 20:49:54 GMT -5
Well..I used another burning program and it worked(Was using Nero and Ultra Iso worked). So I'm currently posting from KNOS 9 RC. What I've discovered thus far..you have to bounce around some on youtube to get flash functioning with FireFox. I don't see the clear flash cache icon any longer but once flash started working, I didn't have any problems.The epiphany browser wouldn't play youtube videos at all. The little loading circle just spun w/o progress. Chromium browser wouldn't load. The little KNOS clock spun and then disappeared and the mouse arrow returned. Tried to load the browser 3 times unsuccessfully. I still don't have any sound for the SoundBlaster Live card from Dell. We've covered that before and I don't expect to get sound since the drivers aren't available. How do you install a printer? Manage printer from applications wouldn't work and manage cups wanted a password. So that's what I've discovered thus far. One final thing: I'm running this on an old 2003 Dell running XP SP3 with one gig of RAM on a Pentium IV. Took awhile to boot from the DVD but expected that. Yeah, dunno why but Nero never worked properly on ISO's ... that's why we had to write up the detailed instructions on other burner programs because Nero seems to come with a lot of machines, but their software is ... flaky. Flash is so bloated that it takes a long time to load from DVD, and often the web site has given up on the load before it's done loading. Thus, Flash sometimes needs a kick in the pants to get going the first time after a bootup. Works fine though from a stick or other, faster media when first lit up. Epiphany should cough up Flash eventually, uses the same library as Firefox. Pity about Epiphany though, that browser dates back to the first KNOS back when we called it "SafetyNet" back in 2007. Sadly the developers haven't done anything with it in nearly two years now and we're seriously considering dropping it. The symptoms you describe suggest that somehow we ran out of memory there. How much memory does that machine have on it? If you want to squirt me diagnostics, be happy to give it a lookover. And as for the sound card, if I remember correctly, that was a stripped down sound blaster "X2" type, right? Only way that could be supported by BSD would be if Dell or Sound Blaster would provide the BSD folks with proper hardware documentation for it. But perhaps there's a possible trick up our sleeves for that if you want to send in the diagnostics and we can see if anything has changed with the BSD 9 kernel as far as spotting what's in there. |
|
|
|
Post by Kevin McAleavey on Mar 11, 2012 5:02:45 GMT -5
One final thing: I'm running this on an old 2003 Dell running XP SP3 with one gig of RAM on a Pentium IV. Took awhile to boot from the DVD but expected that. Ah! My bad! Just saw that you only had one gig there, and being a 2003 vintage Dell, they stole a good bit of that memory for the video on the motherboard so they wouldn't have to provide a proper amount of memory for video. Your actual available memory is somewhere down around 800MB (-128MB for the video and they borrowed some more for something else according to the documentation of how they did things back then) and not the full gigabyte we were expecting available for KNOS. That would explain it. The BSD 9 that KNOS 9 is built on is a bit hungrier for memory than our 8 version, and the XORG video drivers for 9 are even more so. That would definitely explain the kissing the sidewalk there. That machine would be happier with our upcoming 8.3 version which should be out by summer. One of the reasons why we're planning to keep 8.x going for another year and change is older machines where 1GB or thereabouts was typical, as opposed to machines built since 2007/2008 and newer which is why KNOS 9 exists. Nowadays, machines are expected to have 2GB or more "stock" memory installed and of course, with all that abundance, OS coders have gotten more sloppy and have thrown in more stuff simply expecting it to not be a problem, completely forgetting the reality that there are older machines out there in regular use. Something we consider VERY important here at KNOS since we maintain older machines in order to give them "new life" in corporate scenarios with KNOS beyond their expiration dates ... |
|
|
|
Post by Kevin McAleavey on Mar 11, 2012 5:53:31 GMT -5
I still don't have any sound for the SoundBlaster Live card from Dell. And ... just chatted with my guy in Taiwan who did the sound code for sound blaster! He DID do some new code for Creative stuff, although not for your specific card, for BSD 9. He gave me a little trick I'd like to try, but for now since it's a potential risk should others blindly try this trick, I'd like to do this in email to gather the data we need to see if it's covered. I'll have you force load a kernel driver and see if your card is detected. Send me an email to support@ and let's see if his suggestion works to make that card show up. If so, then I missed a chipset identifier (unlikely but possible) and I can fix it in our release. I'm not holding out much hope though since that card should have been detected automatically with BSD's device detection, but perhaps we all missed something in the build ... OH ... and if you're reading this, "moody" ... YOU TOO with that strange "Audigy toy" you didn't get working right in 8 as well. My guy claims that might show up also with the new code and we might possibly wake that up as well. |
|
|
|
Post by moody on Mar 11, 2012 19:43:31 GMT -5
I'll keep 8 around until 8.3 comes out, but by then you'll have to remind me why and what I'm suppose to test it for.
|
|
|
|
Post by Kevin McAleavey on Mar 12, 2012 1:29:58 GMT -5
I'll keep 8 around until 8.3 comes out, but by then you'll have to remind me why and what I'm suppose to test it for. I thought it was you that had that weird Audigy sound card that wasn't detected ... maybe I'm thinking of somebody else? |
|
