What a long week! I spent this whole week taking some SharePoint training classes and my brain is tired. It was kind of nice to be a way from work but I know I have a lot of work to get caught back up on next week. Especially since I’ll be on vacation the week after.
Anyway, back to SharePoint…my company is interested in implementing at least some of SharePoint internally so after playing with it for a while, I decided I probably should take some classes before going any further with it. It’s flexible (almost too flexible) and can be very confusing.
After a week of classes, I have a better understanding of it but I still find pieces of it confusing. There are just a lot screens that look similar and often have similar functionality but you can only get to them in very specific ways. It can be difficult to find the specific screen you need to find. Even the instructor got lost in the interface a few times, so I don’t feel too bad when that happens now.
Overall, I see some great potential in SharePoint but I also see the potential for a lot of work maintaining it. Luckily for now, we’re only going to be using WSS 3.0 and not the full SharePoint 2007 software and we’re only going to roll it out to one department at a time. More than likely, we’ll eventually start using the full version but for now, the basic version will make a big difference…better document management, document versioning, better and easier to use interface than our current Intranet, etc.
I’m excited!
I’m having a random network problem with my laptop that is driving me crazy. The driver for the wireless network card is somehow becoming corrupted and keeps my laptop from going to sleep when I close the lid or when I just put it to sleep manually.
It took me a while just to narrow down what exactly was causing the problem and once I figured it out, it still took a while to find a fix for it. We had to disable the wireless connection before putting it to sleep and then enabling it when we wanted to use it again for quite a while. I finally found the answer on a forum where someone suggested uninstalling the driver and then reinstalling the driver. Unfortunately, this hasn’t stopped the driver from becoming corrupted, if that’s even what’s really happening to it. It seems to be getting worse by the day.
So what exactly does this have to do with Windows besides it being a Windows driver? Well, from my experience, when these random errors begin happening and won’t stop, it usually means it is time to wipe the hard-drive clean and reinstall Windows. This does not make me happy.
Anyway, I guess that’s one more reason why I’m going back to Macs exclusively. I know that running Windows on a Mac is bound to have the same problems eventually, but I won’t be as tied to the OS as I am now. Reinstalling Windows won’t be as big of a deal as it is right now.
I cannot wait to get a new Mac! I’m still holding out until Apple updates the Mac Mini with a faster processor and the 802.11n wireless card. It’s due for an update any day now.