0A stop errors is what I was getting with the bad RAM. I remember this error YEARS ago on a friend who had bought a Micron desktop that had bad cache on the motherboard. He had replaced every other component and eventually it came down to the motherboard. I don't think BIOS's have the option to disable onboard cache anymore.

My money is on bad RAM.

 

I appreciate it guys, I do.

Crucial here I come. (hope that's ok).

Probably talk to Dell at some point as well.

 

to bad RAM

Luckily for you Srika you're running Vista and not XP. Vista has a builtin Memory diagnostic tool not available in XP. So use the built in instant search (also not in XP) by just hitting the start button and type in "memory" you should see the memory diagnostic tool pop up and choose to restart now and check your memory or schedule it to do it next time you restart or turn on your computer.

 

cool on that tool, I ran it -

"no memory errors were detected".

does this mean anything conclusive?

 

try memtest86 then. download and burn to cd

 

FWIW, my case only crashed when the system was under high load: running a full virus scan and installing a service pack. You'd probably want to do something that will consume all available ram. How about loading a gigapixel image in Photoshop? That'd stress the ram out.

I'm sure there's some memory test programs that do the same. memtest86 probably has some good tests.

 

well its been ok last few days.. and I wasn't doing anything when it BSOD'd.

btw does Task Manager show virtual CPU's? It is showing 8 and I thought it would only show 4. And, I didn't think it showed virtual.

 

yes your CPU which is a quad core with hyper-threading will show up as 8 cores.

 

nifty little feature i just noticed

if you are transfering files and you minimize the transfer window, actually it doesnt even have to be minimized.

the icon in the taskbar, it shows as a meter showing how much has been transferred.

 

I saw that in a blog post about the Win7 Taskbar. I'm excited to start coding for some of these features.

http://msdnrss.thecoderblogs.com/200...dows-7-taskbar

 

 

I love that. It's so true. I was thinking of that comic yesterday.

 

this computer is horrible. after using this for a good several days I went back to work today and my computer there feels like molasses. its a C2D 1.8 desktop with 2GB. my laptop feels horrendously slow as well.

can't imagine how fast this would be with XP!

 

FYI -

http://isc.sans.org/diary.html?storyid=6808

 

I've been playing with the RTM code of Enterprise edition for the past few days and apparently desktop search can only index items local to the workstation just like all the other previous versions. If you want to index and search your Exchange mailbox you still have to be running Outlook in cached Exchange mode which, of course, sucks the proverbial monkey attachments. Not terribly unexpected but pretty damn disappointing in this day and age. What's a real killer though is that you can't even add a network file share to the indexed locations so an average user can't even have the OS' built in search keep track of what's in their network home directory.

:thumbsdow

 

They removed it from the advanced options?

 

umm, it will search servers via Federated search which is new in 2008 R2. It will search other Win 7 PCs on home networks if their a member of HomeGroup. And AFAIK you can add a network share to the library which would make it searchable. I know I've searched my other Win7 machines before.

For example Windows Home Server Power Pack 3 which should be available shortly has built-in Windows 7 enhancements that automatically add the share folders on the WHS to the Win7 libraries which makes them easy to browse also WHS PP3 comes with Windows Search 4.0, which improves server-based searches performed from Windows 7-based PCs. Non of this stuff is proprietary to WHS, just automated.

Search 4.0 can be had here and I think it was included with Vista SP1
http://www.microsoft.com/windows/pro...wssearch4.mspx

I'll assume these W7 machines are on a domain which then changes everything. you can't use HomeGroup in a domain. Isn't there a windows search server thing in Server 2008, I've seen it before but can't remember the exact name.

 

yes this has been removed, I never knew it was there. but now you just add the share to the library and that should do it. I think. I can't test it right now to confirm or deny, cancel or allow.

 

Here is the entirety of the indexing options when you open it up in control panel. The window on the right is after clicking "show all locations" and authenticating as a local admin. Maybe I'm missing something but I don't see any references to the library. Hell, there isn't even an "add" button in either of these boxes. It just shows you everything that's local to your machine and that's all you have to pick from.

 

I attempted to add a new library for the UNC path of my test user's home directory and got a message saying that the folder couldn't be added because it wasn't indexed. The resulting help link stated...

Teh Suck.

 

What's wrong with that? Just make sure you have search 4.0 (which comes included in W7, Vista SP1, Server 2008 and R2, also avail for download for XP and server 2003) running on that PC and that the folder is in that PCs index and you're good. I think they did this to reduce network traffic and increase the accuracy of your local index file. Otherwise everytime there was a change in a file on another PC that was in your index how does it notify you? by sending out a message to all the other PCs on the network that hey this file has changed, that's unnecessary network noise. Instead your PC will check with the other PCs index file when you search for that file, instead of that PC unnecessarily blasting out status updates everytime an indexed file has changed.

 

switching gears here but you know, i really dig the snipping tool. can't remember if i even had it on my vista business install but its pretty handy.

 

yes it been there since vista. In win7 they changed the default format from Jpeg to png cause the jpeg pic in vista was too compressed but in W7 it's fine.

 

I was poking around in the Windows Search service and registry entries and figured it would be simple to add a new rule to search a network share in the key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\CrawlScopeManager\Windows\SystemIndex\Defau ltRules

But then when I was restarting the Windows Search service, it dawned on me. The search service is running as the local system account. It's not going to have any network credentials to scan any network shares. I tried setting the service logon to the domain administrator, but then it didn't have some local privilege to run. I gave up after that. If anyone else wants to try hacking that out, go for it.

 

I'm not following your line of reasoning here. I think that's because you may be talking about a P2P setup (i.e. your homegroup) and I'm talking about a typical corporate user who's logged in as a domain account on a machine that's a member of the domain.

In my situation it looks like Microsoft is saying you need to run and administer federated search in your environment just to facilitate individual users searching their own home directory and/or mailbox. This is what qualifies as teh suck in my book.

 

I can think of a few reasons why Windows Search shouldn't allow network searches.

Security: If you have three users on one machine and the catalog on the hard drive contains indexes and excerpts from those three users, it wouldn't be too difficult to extract other users' information from the catalog files. Like I mentioned, the search service runs as the local system account. To accommodate multiple users on a workstation, the service would either need to run as a user that has access to everyone's files on the network (a definite security risk), or impersonate the currently logged-in user (a probable security risk).

Performance: If you have a user that logs in to multiple workstations, every time the user logs in, it's going to rescan the network folders for indexing. That could be significant bandwidth. Whereas the federated search catalog is probably maintained locally on the server and a query is sent to the search service on the server.

Maintainability: When you validate an index on a network share, what is the difference between not being able to verify a file because the server is temporarily unavailable and not being able to verify a file because the server is permanently unavailable? If you have all your files on \\server1\share and now you've moved them to \\server2\share, you're going to get duplicate results in your search and half the results are invalid.

Moving the search function to the server itself solves all three of these issues.

 

Sorry, but I can't view the fact that the search service runs as local system as being anything but a gaff on Microsoft's part. Besides, how does security work in the P2P "homegroup" environment? The local system account on machine A has no rights to anything on machine B.

Regarding your other points, I would be willing to bet that > 90% of all end users in the setting I describe only log into a single machine. I would also be willing to bet that if those same end users experienced a server failure of some sort that required their files to be moved, those people would give two shits if it takes a week to get the search indexes from the other server restored. If a server goes down, the only thing that's going to concern those users is getting access to their files again as quickly as possible. Getting search capability back will (and should) be a much lower priority. Now if these two things really do concern you then fine, run the full fledged federated search. Again though, I would be willing to bet that a significant percentage of people would be just fine with purely desktop-based solution and its inherent limitations.

Where I'm coming from with all this is that there is a third party application, X1 Professional Client, which has for years been providing desktop search capabilities for Exchange mailboxes and files on network shares without any problems. It just so happens that A) this is third party application which not only costs money but has its own interface users need to learn and B) it's simply not designed that well from perspective of the end user interface. It absolutely does work though.

Regardless, the fact that this program has existed for years tells me that Microsoft simply doesn't care about providing providing this functionality to end users in a manner that is reasonable for small to mid-sized organization to implement.

 

I will say that MS is probably having a very difficult time continuing to satisfy small-midsize companies while at the same time trying to create some massive enterprise features that are just overkill.

 

^^Microsoft certainly isn't alone in that regard.

BTW, I should clarify that for all bitching on this subject of the desktop search, I really don't hold it as much of a knock against the OS itself. If something isn't in the box, then it's simply not there. In my view that's a Microsoft decision making issue and not really any sign of Win 7's "quality." Overall, I can't really think of any actual problems I've had with it so far.

 

When XP came out it's enterprise adoption rate was about 12%. Well they're expecting Win7 to blow that away.



So far Intel and BMW have announced that they're upgrading to Windows 7 immediately. I think alot of the demand for W7 is cause a lot of businesses skipped over Vista and XP is getting really outdated on them.

http://windows7center.com/news/windo...ster-than-xps/

 

This is one of the new computers coming with Windows 7. Awesome!

A multi-touch capacitive screen tablet with pressure sensitive stylus (like a Wacom), SSD, 3g, VGA, HDMI, extra drive bay that you can put an extra battery in, ambient light sensor, fingerprint scanner and all the usuals.

<object classid="clsid27CDB6E-AE6D-11cf-96B8-444553540000" width="437" height="347" id="viddler"><param name="movie" value="http://www.viddler.com/simple_on_site/7d8930a2" /><param name="allowScriptAccess" value="always" /><param name="allowFullScreen" value="true" /><embed src="http://www.viddler.com/simple_on_site/7d8930a2" width="437" height="347" type="application/x-shockwave-flash" allowScriptAccess="always" allowFullScreen="true" name="viddler" ></embed></object>

 

Dialect survey question #123

40. Gesture

 

 

 

LOL at that growth rate chart.

 

WTF! I'm still running RC code and now I can't install RSAT for Windows 7 cause I'm RC. They had a version that worked with RC but you can't download it from them anymore. Time to check sourceforge and softpedia.

I've downloaded Hyper-V 2008 R2 and wanted to get it up and running. I've installed it and set it up but to manage you have to use RSAT but alas....

 

Welcome to the world of real IT. Microsoft has a long glowing history of their server admin tools and pre-release versions being matches made in Hell. This is true of both pre-release admin tools as well as pre-release desktop operating systems.

The worst case was the adminpak.msi from a pre-release version of Server 2003. I don't recall if it was beta or RC, but it was available to the public as an individual download from the M$ web site. Regardless, if you put this thing on your XP machine, you could never uninstall it. Ever. Period. And the adminpak.msi from the RTM code would not install over the top of this pre-release version. The only way you could get rid of the pre-release adminpak and install the RTM version was to format your computer.

 

HA! I almost experienced that last night. There's a new leaked built of Office 2010 out there and I wanted to install it but I still had the previous version on there and it refused to be uninstalled or modified. I had to go and manually delete all the files from program files, app data, temp, program data and then go through and delete registry keys and then reboot. It worked after that, thankfully. So if I were to find the RSAT tools for W7 RC would that would on RTM Server 2008R2?

 

You got me at this point. Since we have no production servers on 2008 or 2008 R2 I have yet to try the RSAT on any Win7 install so I couldn't tell you what would have worked on the desktop RC code.

 

Well I'm burning a copy of VMWare's free ESX Server as I type. So I'll try it out and see how it goes.