Spooky

You mean a SCX-4216F? There aren't any Vista drivers for the 4216F. Samsung is bad about drivers anyway, the drivers they produce are for what ever OS was most plentiful at the time the product was produced with no support for future OS's in terms of drivers even when the OS is released. This is one of the reasons I don't like Samsung products.

If i'm not mistaken you need the Microsoft Windows Key Management Service MOM pack for monitoring and reporting for activations in KMS 2.x (I assume this is what your using since this is a Vista forum). Its due to be released in first quarter 2007. You may be able to find out more here: KMS Activity Reporting Is this what your asking? Its assumed that the computers registering on your KMS are also on your network and that you have taken steps to ensure that only the computers with the proper keys for your KMS are registered, since only those with the proper keys can activate via a KMS which only accepts certain keys issued to your company. As far as managing those computers its assumed that normal network management principals are applied. (Did I say that right? Its early and I need more coffee)

Here is what I found in real world testing with actual systems and people; I know MS said that 1.5GB was about the limit for seeing decreasing effectivness for ReadyBoost but my own testing on over 30 machines, and with input from 100 advanced intensive use Vista users I know, over a period of a month shows the more realistic limit is 1GB of RAM. Between 1GB and 2 GB (and at 1.5GB) of RAM I saw a very sharp, to mostly non-existant, decrease in ReadyBoost effectiveness. Its effectivness was greatest at 512 MB RAM. This was informal testing, did not test things like speed for example, and only considered an actual visible and noticible improvement from ReadyBoost. The re-boot or re-start sceinario was not tested because it is not true that ReadyBoost improves Vista start-up speeds, however, while in Vista actual applications were timed for start-up and on the 512MB systems there was a noticible improvement on most applications start up time and their responsivness while in use. So...what I was looking at is what actually happens rather then what could be because in the end the proof is in the actual effectiveness and usage. 512 - 1GB RAM = Improvement on most systems. 1GB - 2GB RAM = Some improvement but not as great as with below 1GB RAM. Will see decreasing effectiveness for ReadyBoost. While effectiveness was decreased greatly in this range compared to usage on machines with 512MB RAM (approximately 75% less effective) it was noted (very informally) that there seemed to have been a effectiveness peak at 1.5 GB because between 1.5 GB to 2GB ReadyBoost effectiveness became almost non-existant. (maybe this is what MS was saying about the 1.5GB thing?) 2GB RAM and up = No improvement from ReadyBoost at all. Every once and a while the USB device LED flashed very briefly indicating access for ReadyBoost, I saw it flash maybe twice during a two week daily usage on one particular machine I use constantly. Not worth even considering a USB device for ReadyBoost if using 2GB RAM or above. Its been reported to me by others that what I saw was what they were seeing also for ReadyBoost usage so I think i'm on the right track. A few people with 2GB of RAM reported to me that they did see some increased light ReadyBoost activity a few times during each of their sessions while they were using Photo Shop for some graphics work but while not using Photo Shop their ReadyBoost activity was in line with what I found for 2GB or more RAM. So, my own opinion is if you have 512 to 1GB of RAM then you might benefit from ReadyBoost.

Disable file and printer sharing and client for microsoft networks for the connection. Don't disable dcom in Vista, it can be done, but its not a good idea. The RPC is open because there are a ton of things in Vista that rely on it, for example Superfetch relies on RPC so if you kill RPC then Superfetch will be adversly affected, and this is a brief reason why you shouldn't disable Dcom in Vista. Its open just like any other port on your computer is open for various reasons, and there is a reason for it to be open. The simple fact that it happens to be on port 135 doesn't necessarly mean its a bad thing, its not like past windows versions were and the advice about port 135 being a 'hidden server' and a danger doesn't necessarly hold true for Vista. Don't use that Dcom thing from GRC on Vista, and the information for Dcom on GRC and that other site doesn't hold true for Vista. Even if you found a way to disable every single port in windows you would still have ports open if the system was to run at all and port 135 is no different in this respect for Vista. If you set up the correct connection type for your connection and haven't done anything to the Vista firewall and disabled file and printer sharing and client for microsoft networks for the connection then even though port 135 shows as open it shouldn't be open to the outside world and to verfy that go to GRC.com or PCFlank or one of the many sites on the net and run one of their scan/stealth tests, if Vista is healthy and everything is set up properly then you should show as 100% stealthed with a standard Vista default install, if you don't then something is not right. There are numerous pieces of software that will expose port 135 also, many of the P2P clients will expose port 135 intermitantly for example. If it continues to bother you thats its open and you really want a 'peace of mind' thing then just set up an inbound and outbound rule in the firewall to block it for everything.

It wasn't omitted, its right there in Control Panel Start\Control Panel\Default Programs\'Associate a file type or protocol with a program' A month?

Well, it was attached before but i guess the recent board update did away with it. Here it is attached again. You can disable driver signing in the GPE and the desktop search service within Vista its self. I see no *.reg file ??? And has someone made a tweak yet to disable the windows-desktop search service? Also, to disable driver signing? vista_reg_tweaks.zip

This registry tweak sets the AFD buffer to 1024. Setting this value in the Vista registry increases the number of messages sent before flow control is imposed. This increases throughput speed some (not bandwidth) and helps out with browsing etc.... Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AFD\Parameters] "BufferMultiplier"=dword:00000400 This value does not normally exist in the Vista registry.

Nah, its the same thing to get it installed on Longhorn

You can get PowerShell to work on Vista RTM. This may help you out: How to get PowerShell on Vista Or here: PowerShell on Vista

ReadyBoost works as intended but not for everyone. On the practical side, if you have for example only 512 MB of RAM in the computer and you plug in say for example a 1GB flash device then most people are going to see an improvement in performance, however, computers with 2GB or more of RAM are not going to see that much of an improvement and maybe none at all. I think the practical limit for ReadyBoost is about 1 GB before very little to no improvement is noted. Is it an 'emergency solution' thing? No, not really, maybe one could look at it that way but to be honest ReadyBoost is more of a novelity then anything at this point and a short term help to some. I guess if someone couldn't aford to upgrade their RAM right now and was in the 512 MB situation then ReadyBoost would help, but is it a real solution? Not really, the real solution is to add more actual RAM. Now it would probably be different if flash devices had read and write times on par with, or better then, that of machine RAM and motherboards accepted flash devices as part of the machines memory rather then an added storage device then plugging in a flash device would be like adding RAM. So what is ReadyBoost in the practical sense? Its basically a novelty item to many, but a help to some, but over all its not a real memory solution for anyone. One of the problems with using ReadyBoost is that MS just threw it out there with Vista with some basic specs, but the flash device portion of the industry doesn't publish their specs for the most part so its hard to tell when you look at a device if it will work with ReadyBoost or not in centext with the MS specs. The reason that industry doesn't publish the specs is because for the most part when they build flash devices the sources for their chips are always changing in terms of speed and quality. Sure, for the most part they are suitable for storage, but if they were to publish specs for example that exceeded the MS specs and claimed their devices were ReadyBoost compatable then it would really put them in a bind because then they would have to add testing for every chip used in building the flash device to market and this would increase costs on flash devices by at least two to three times what they are now, and then consider that some would work for some people and wouldn't work for others leading to a return and tech support nightmare for these companies to support specs that MS set without consideration for what actually is in the real world. Here's one persons experience with ReadyBoost: With and Without ReadyBoost And....here is some good info on ReadyBoost: Tom Archers Blog entry for ReadyBoost

It doesn't matter what they do to it as long as it remains 'web-centric and internet/network orientated' because unless we get some real broadband connections in the US (like the 45 MB/s connections in Japan) like the phone company promised us back in the 90's (but later decided not to do it, they made this promise to win concessions from Congress which they got), were gonna be up S*** creek as far as using something like Vienna. You guys do know that MS's future aim is a move back to a 'main frame' type set up where a windows computer is simply acting as a terminal running applications off the MS servers. I think we will see something sort of like that with Vienna where certain content and applications will need to check with MS before they will run.

Yep, your right, however, the newer flash devices are good for about 10 years with millions of writes. Besides, Vista doesn't wear the flash device out anyway as ReadyBoost is not the intensive write thing everyone seems to think it is, and when Vista reads or writes to the device its doing just what the device was made for which is reading and writing to.

Windows must be really, really really, new to you.

You can move the documents & videos & music folders, use the example I posted. You just can't move the actual User folder but you can move the documents & videos & music from the User folder to somewhere else. You could try a symlink, but Vista isn't going to allow a symlink with the name 'Users' on the same drive with the actual 'Users' folder to function properly for what you want to do. Whats wrong with the Users folder right where it is to begin with...unless your trying to remote profiles....or trying to link to other user folders on machines on a network or across the internet which means that....ahhhh! Uh Oh..... tell me your not going to try that. isn't there a nice trick to make a symlink of C:\Users to point to D:\ the Location of a folder is familiar, but I want to move all the documents & videos & music etc... I think there should be a way like it could be done in XP...

The fact that it will read anything indicates basic functionality. As for the other stuff - RC1 is not a good platform upon which to base solid functionality judgement, however, it might help you out if you were to upgrade DVD drive firmware.

I just posted this in the Vista Tips and tricks section. Its a little trick I discovered that might help someone out with determining if their USB device is or is not actually ReadyBoost capable even if Vista has told you its not because Vista might not be telling you the whole story. How to actually determine if your USB device will work with ReadyBoost and how to make it work if it will - even if Vista told you other wise.

The way Vista tests a USB flash device for use with ReadyBoost can be a little 'deceptive'. Some USB flash devices will initially test as not compatable, however, they may really be compatable. Theres a little trick to it that the average user may not realize, and this may be the reason why some USB flash devices are not listed in the various lists on line as compatable with ReadyBoost when in actuality they may be compatable. When you first plug a USB flash drive in Vista comes up and asks you what you want to do with it, one of the options is to use it to speed up your system, click on this and Vista will check the flash device for compatability with ReadyBoost. The problem is that the very first test may not be accurate if it comes back and tells you that the device can't be used for ReadyBoost when it may be perfectly capable for use with ReadyBoost. So...here's the trick to determine if your device is or is not compatable with ReadyBoost; 1. Insert the USB flash device, and let Vista detect the device. When it comes up and asks you want you want to do close the GUI and do not make any selection. 2. Next, go to USB Flash device in explorer or disk management and format the device. Format the USB device you plan to use for ReadyBoost with NTFS and cluster sizes of 4096. Name the drive something you want like 'My_ReadyBoost' or something. 3. After the format is complete right click on the USB device and choose 'Properties' then the 'ReadyBoost' tab. 4. On the ReadyBoost tab unckeck the box to stop testing the device every time. 5. Next, click the Test again button. If the tab changes from the test tab to a tab that gives you two options of 'Do not use this device' and 'Use this device'. Check the 'Use this device' box and do not make any other changes on the tab especially to the 'Space to reserve for system speed' slider, leave the 'Space to reserve for system speed' setting at what ever Vista recommended. 6. Click 'Apply' then 'OK'. Your almost done - go to step 7 7. After completing the above steps go back to the tab in step 5 and check the 'Do not use this device' item. Then in explorer re-format the device as FAT32. After re-format go back to the tab in step 5 and check the 'Use this device' item. Now your done, and if your device is truely compatable you can now use the device for ReadyBoost. The fact that the tab changes is not a true indication of ReadyBoost capability. Some flash devices may in fact allow this tab to be shown and still not be ReadyBoost capable. To determine if your device will indeed be ReadyBoost capable look on the flash device after you complete the above steps, if a file named ReadyBoost.sfcache exists on the flash device and the flash device is actually being used when you access any hard drive in your computer to start up an application then congratulations as your device may actually be ReadyBoost capable even if it initially tested as not capable. May or may not work for all USB flash devices, If the tab with the two options in step 5 above will not come up, or the file named ReadyBoost.sfcache does not appear on the device, then the device is truly not compatable with ReadyBoost so you will not be able to use it for that purpose. The flash device must handle a capacity of between 2 to 3 times your installed RAM. While your using the device as a ReadyBoost drive you can't use it for normal storage purposes you can only use it for ReadyBoost. The ReadyBoost device must be USB 2.0 and the USB port your plugging it into must also be USB 2.0. I stumbled across this when an IT friend of mine gave me a call and told me that all 30 of the company purchased Verbatim 4GB Store and Go USB Flash devices were giving mixed results for ReadyBoost with several different machine models. Some would pick the Store and Go USB Flash drives right up and let you know the devices were ReadyBoost compatable and didn't need further testing by Vista. Some machines would not detect the device as compatable. We knew the flash devices were ReadyBoost capable because some machines were using them just fine and detected them as compatable, so we came to the conclusion that differences in chipsets may be the dividing factor because on the machines with certain chipsets the devices would be detected and used just fine with ReadyBoost but the exact same Verbatim 4GB Store and Go USB Flash device plugged into a machine with a different chipset would not initially sucessfully test as ReadyBoost capable. After doing this little trick, all the machines that tested the USB device as not ReadyBoost compatable intially were now using the devices in a ReadyBoost capacity without complaint. There was a noticible improvement in speed of the system, it varied between systems, but there was a difference. So...you be the judge, give it a try and see what happens, it can't hurt. Hope this helps someone out.

heres an example for the documents folder, but i don't think you can move the user folder cause its actually part of the OS and contains system folders and Vista expects it to be in its partition and Vista will only let you move user data folders but not system folders in the users folders. (did I say that right?) Here’s how to move the Documents folder: 1. Open Windows Explorer, navigate to the empty drive that you want to use to store data, and create new folders for each of the existing folders you want to move. If you’re the only user on your computer, you can put them in the root of the drive: D:\Documents, D:\Music, and so on. If you’re planning to use the drive to store data for two or more users, you should create a separate top-level folder for each user and then create subfolders for each type of data, eg... D:\NewLocation\Documents, etc. 2. Click Start and click the bold user name at the top of the right column in the Start menu. This opens your profile folder. 3. Right-click the icon for the Documents folder and choose Properties. 4. On the Location tab, click the Move button. 5. In the Select a Destination dialog box, double-click Computer, double-click the icon for your data drive (D: in this example), and select the folder you want to use as the new location. Don’t double-click this folder, just click to select it. 6. Click Select Folder to return to the Location tab, and then click OK. You will see two dialog boxes: Do you still want to proceed and redirect to <new folder location>? Click Yes. Would you like to move all of the files in your old location to the new location…? Click Yes. (If you click No, the original folder remains intact and you risk having documents split between the two locations.) OK, your done. You can now repeat the process for Music, Pictures, Videos, and any other data folders you want to use. When you click the Documents shortcut on the Start menu, it takes you to the new location, which appears to be in the same old location. In the Vista namespace, your profile folder always appears under the Desktop, and each link in that folder points to the location you specify. So you can leave some folders (like those you rarely use) in the original location and just move those that contain files/data.

How sad.

Its not fake, its just not really infra red, its thermal. Many Forward Looking Infra-Red (FLIR) units have the capability to switch from just infrared to thermal. I think its either a hand held or mounted unit. You can buy a unit on line that will do the same thing as this little video shows. I happen to have one I bought a year ago, cost me $1800.00 for a nice hand held unit, we use it to record and track temperture change distribution in ceramic circuit board substrates. But that doesn't mean we don't have a little fun with it too

She's a total id***. She assumes that the PC is the monitor shes been looking at all the time and when someone tries to explain to her shes too self centered to realize that others know things also and refuses to listen because she assumes she is right and they are wrong, she obviously has lived in a world that revolves only around her where she is right all the time. People like this are a good argument for birth control. I wonder if anyone has ever tried to explain the birds and the bees to her, she would have a melt down. I'm going to go claim the reward from that village that was looking for its id***, I found her.

My daughter uses Emigrant, she likes it.

Thise aren't error messages, its asking you what you want to do because either it doesn't recognize the inserted media or it doesn't recognize the full capabilities of the drive (or really the drive its self even tho it shows up. have you tried updating the firmware on the drive?

Setting it from the Local Security Policy doesn't do what you think it does. The local Security Policy only uses the already present menu item to accomplish its settings. Using it from the start menu or Local Security Policy doesn't do anything to prevent something with administrator privilages from over-riding a rule. The reason that Local Security Policy seems to have the effect your seeing is because the Vista default is to check Local Security Policies first before anything else and apply those policies before anything else, so setting a rule to block or allow something in the Local Security Policy will be used before the existing firewall rule. The Vista firewall is different then other firewalls, the rules are not tested one at a time, they are all tested together at the same time including the Local Security Policy (checked first). You enable logging by opening up the advanced firewall GUI, highlight 'Windows Firewall with Advanced Security' at the top of the firewall GUI, then click 'Action' then 'Properties' then choose your connection profile tab, then click on the 'Customize' button in the 'Logging' area on your connection profile tab.

If you don't want any other users to have admin privilages then don't put them in the admin group. Remember, on install the first account created is in the admin group, but accounts you create after that are not in the admin group. If you want the admin account to be only available to you then password it with a password known only to you. I want both user active all the time, just the Administrator be accessible by me only... OK, thanks, I got the idea...