elaverick

As I understand it Windows Vista comes in both 32-bit and 64-bit flavours on all media and the user gets to choose at installation time which copy of Vista they want to run with... Now I've just received my copies of Vista in my Microsoft Action Pack kit however I can see no way to select whether I want to install a 32 or 64 bit version of Vista and I'm automatically lumbered with the 32 bit version. I was originally upgrading from a copy of XP Pro x64 (so you would think this would give them a fair clue as to the direction I wanted to go in) but I've been completely unable to find anyway of selecting my particular poison. Does anyone have any insight as to what is required to get the 64 bit OS up and running from these DVD's?

That got it thanks. Turns out it was set for Read & Execute rights for named Administrators but no more... the folder that had been confusing me orignally was set for R&E rights for everyone but you couldn't take ownership as the Add and edit buttons were greyed... that was because the folder was shared as well. Thanks for the tip

What kind of reboots are we talking? Is it just a complete restart as tho someone had hit a reset button or do you get a BSOD first? If it's like a reset switch type reboot then the next question is do you have a lot of drives/peripherals attached? I spent months trying to track down a reboot like that only to discover that the problem was the fact that I'd bought a really cheap and nasty generic PSU that had low stability across its +12v rail.

I recently decided to join my PC to a Windows 2003 Server AD domain to get a little practise with adminstering systems in an AD environ. Now as a strange side effect I've found that some of the folders on my second partion D: have set themselves as Read Only and subsequently all the files in them are read only also. Now as folders themselves cannot have read-only attributes this means I'm unable to unset the read only attribute and get the error "access is denied" any time I try. This is the case wether I am logged onto the PC locally or as a user listed in the AD. I'd really appriciate suggestions from anyone on how to fix this as it's getting VERY annoying. Title edited -- Please, use [TAGS] in your topic's title. Follow new rules --Sonic

We'll I've just grabbed SP2 and so far most of it seems to work ok... however: If you have the WidComm Bluetooth stack installed it seems to kill that fairly instantly. I have however now uninstalled WidComm and tried using SP2s native Bluetooth stack. Bits of it seem to work quite well however anyone with serious(?) Bluetooth needs have a couple of points to consider right now. SP2 BT has quite a limited set of services supported. Dial-up Networking Keyboards & Mice OBEX File Transfer Personal Area Networking (PAN) Serial Ports Printing This means anyone with experience of WidComm's feature set will miss: Audio Headset Audio Gateway Fax PIM Sync So far I haven't tried to re-install the WidComm stack but I suspect it will continue to fail (I'd like to know if this is incorrect however). On the plus side MRouter (For Symbian OS devices) detected things absolutly fine and I think this stack might be slightly nicer about allowing multiple device connections (but as the only other BT device I have is a headset I can't be sure) as it assigns each device its own Com ports. I'd be interested in anyone elses experiences with BT support especially if they have a method for enabling headset profiles.

Now I've only just found this, so I assume the rest of the world figured this out long ago however it might be of use to someone else... First off if like me you get lots of people wanting to borrow you XP CD's (cos they've 'misplaced' theirs) but you want to include a load of little extras on your CD (I have Visual Studio which most of my friends tend not to want... or understand), you could include a line in whatever batch file you run from cmdlines.txt such as... if not exist a:\nostudio.txt regedit /s VStudio.reg This way if you want to avoid a component being installed all you do is create a blank text file on a floppy disk called nostudio.txt (or whatever) and if it's found that component will not be installed. Just remeber if you are splitting you installation registry files into multiple segments (I have options for both Visual Studio and OfficeXP) that you still have to continue the consecutive numbering of the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx statements otherwise they will overwrite each other and things will be missed out of the install. The second thing I found (which is really REALLY obvious I know...) but if you are adding registry values of: [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\zz107] 1="dosomething.exe" "Were doing something or other" You can also include a 2= and a 3= etc... This is great if you want just the one line to explain what stage your installation is at such as "Installing Microsoft Visual Studio 6" as opposed to "Preinstalling VS6" and "Really installing VS6 now". I know these are both fairly obvious things but I hope someone will have a use for them.