
Spooky
MemberContent Type
Profiles
Forums
Events
Everything posted by Spooky
-
Using Cdimage Gui To Make Vista Rc2 Image File
Spooky replied to SyntaxError's topic in Unattended Windows Vista/Server 2008
is this boot sector from the x86 or x64 RTM DVD? Attached is the boot image extracted from Vista RTM DVD for those that want to use it Enjoy! -
what's the differience between Manage and Administrate?
Spooky replied to wbpluto's topic in General Discussion
Administrate means (according to the dictionary) (and briefly in plain english); is performing the act or process of administering, as in, the execution of duties. An administrator performs the act but doesn't make policy, only execues or applies the policies. Manage (according to the dictionary) (and briefly in plain english); is to handle or direct with a degree of skill. To exercise executive, administrative, supervisory direction of a business. A manager for example carries out the excutive, administrative, or supervisory, policies passed down to him/her in a manner that achieves the desired outcome. Like a store manager oversees the employees and ensures company policy is carried out. To put things into context: the policy makers establish the policy - the administrator applies the policy (passes them down to the manager), and the manager carries out the policy. Kind of almost the same but different, but close enough to be almost the same. Most times they are interchangeable. The key difference being the skill level. The manager is generally closer to the activity to which the policies will be applied so they need a larger degree of skill to understand how the policy fits into the activity picture and where it needs to be applied so they can be applied in the most effective manner. On the other hand, the administrator is generally not that close to the action but wants the policies applied. The administrator generally over sees many parts of the same entity and relies on the manager at each part to get the job done. Sort of like a regional manager oversees the managers at different locations. -
autoct, "The problem come when it try to format or quick format, it start and then tell me that it can't" The reason is; Vista will not let you just re-format its partition. You will need to delete the Vista partition first then recreate a partition before you can format.
-
I'm assuming that you want to get rid of Vista and use the partition its presently on to install XP....right? If so, you will need to delete the partition Vista is on first, then create a partion, then format that partition.
-
Some say the autounattend.xml works great from the root of the dvd, others say it doesn't. My own personal experiences are that i've not had any problem with having the autounattend.xml work from the root of the DVD, but that doesn't mean it will always be that way if something is changed too drastically in building the un-attend install DVD in the future. We might need to explore this a little closer to see when it will work and not work from the root of the DVD. I hate having to keep a diskette around just for an autounattend.xml file, i'd rather have it on the DVD. A nice neat 'pop in the DVD' and forget about it thing. lol fair enough. The problem i have found though is that the autounattend.xml/unattend.xml is not working from the source on my RTM release. Further, if you have options specified in the <DiskConfiguration></DiskConfiguration> area and boot from the DVD these settings appear to be ignored, however if you have the autounattend.xml on a floppy/USB drive they work correctly.
-
If the drive is good then something has got to work. let the drive you want to reformat be the only drive in the system, boot on one of the CD's I mentioned above (if you have something like that, if not try a win98 boot disk with format on it) and format the drive. Then shut down, replace the drive with the one you want and format it then install Vista but during the install choose to reformat the drive for NTFS.
-
I wouldn't expect to see Vista fit on a single CD anytime soon. The very basic core components of Vista alone weigh in at 1 GB. thanks amigafan thats exactly what i wanted to know 107xMB-220MB = ~850MB another 150ish MB please *dreams* for homeBasic users, will it be possible to remove features of other versions which are included on the disc?
-
did you bridge the connections? Briefly; One difference between the 'public' network and the 'private' network in Vista is one is discoverable and the other itsn't (not entirely). You can read the help for more info. It doesn't determine what you can and can not share, it depends on how your set up however. If you were on a LAN then it would be correct for Vista to expose ports on a private connection because it expects those to be controlled some place else in the LAN and sees your machine as the client and not the server, so....If you establish a private network on the Vista client and your not on a LAN then it will open ports like its supposed to for a LAN...and this brings us back to the firewall - even though you can turn it off in a private network you should have something in your router that does the firewall thing for you. What is sounds like is that you may need to configure the connections as a home connection and then bridge your two seperate connections (your two NIC's), then decide what you want to share.
-
ERROR Opening the vista WIM image file ! could you help me.?
Spooky replied to Robell_Liu's topic in Windows Vista
Robell_Liu; Can you actually install Vista? If you can install Vista then the .wim most likely wasn't corrupted. So if you got the .wim from the same DVD he installed Vista with it shouldn't be corrupted. But...ya never know. Indeed... -
I would kind of expect some 64 bit machines to have some type of issue with the 32 bit version installed. The issues you outlined are not uncommon with the x86 32 bit version installed on a 64 bit system. "Big enough, 25gb, as I mention in my post things were fine with 64bit RC2, but not with 32bit RC1" RC1 still had a lot of problems so maybe you were experiencing some of those when it saw the system was 64 bit it couldn't cope instead of 32 bit like it expected.. Overclocking can be a problem with the 32 bit version installed in a 64 bit environment. You would think installing the 32 bit version on a 64 bit machine that you wouldn't see issues like this but thats not exactly a valid thought because some systems will see these issues occur. Its one of the reason they make seperate 32 bit and 64 bit versions. The right tool for the right job usually helps mitigate problems on the job - square peg in a round hole. Its like putting over sized tires on your car, they might look pretty and cool, satisfy your need, but the issues introduced are additional stress on the transmission - axel - gas mileage - engine, all because the car wasn't made with them in mind. Might work for a while but the problems will eventually get you. No, I installed the 32bit on a 64bit machine... Big enough, 25gb, as I mention in my post things were fine with 64bit RC2, but not with 32bit RC1..I cant see overcloking was the problem, as RC2 64bit was fine.. just seems tobe consistant with 32bit Vista and my pc, for whatever reason....
-
"with with my 64bit rig..." I'm a little confused by your post so just a silly question....you installed the x64 version on a 64 bit machine...right...and you installed the x32 version on a 32 bit machine...right?
-
did you follow the instructions for rebuilding the .iso outlined in the help? Believe me, I´ve done so..! also workin by copy´n´paste.. Another idea?
-
Read the WAIK help, it tells how to do this and it works because i've done it.
-
"WinBeta AIO DVD" "so far in my testing it's this simple: vLite doesn't work on the WinBeta AIO DVD release" Ahhhhh...isn't discussion of improperly obtained or distributed, or pirated software, taboo here? Thought so... "You need to get an unmodified AIO disc, either from Microsoft or some other source" Theres no such thing as a legitimate AIO disc for Vista from MS. "I located a real Vista RTM ISO" Hmmm...OK....
-
Sometimes Vista will not let you reformat a drive partition that has an OS on it from within Vista. This is mostly because Vista wants that old partition gone and wants you to delete an old partion then recreate a new partiton on drives it manages. Don't format hard drives from explorer that have operating systems on them, use disk management as Vista views drives with operating systems on them as management tasks and not just drives to hold information and files. Try these first; 1. In the Vista drive management, right click on the drive and choose to delete the partition. Then create a new partition - it should let you format the drive now after the new partition is created, however, for some reason with some older drives you may need to reboot back into Vista to continue the format. 2. If #1 doesn't work, try opening up an admin command prompt and using the format command from there. 3. If #2 or #1 doesn't work boot a rescue type CD that will allow you access a command prompt, something like Bart's or winPE or something like that. Then format the drive from there. Or you could use a partition management type software and boot on that. 4. If #1 - #3 fail, then remove the new hard drive, put the old one back in and do step #3. Then when its done, put your new drive back in as your bootable drive (i.e... C:\) and if you want plug the old drive in as a secondary some where, and away ya go. Play around a little with #1 first.
-
use the help in Vista and search for Activate or Activation.
-
Personally myself I would have gone with the Raptor
-
You can also turn off the welcome center in the GUI after on the second reboot after the install is complete, and from then on after, by just unchecking the box in the lower left corner about not showing it when Vista starts. The reg tweak, however, does come in handy for an un-attended install set-up.
-
I doubt if MS leaked it. Can you imagine what would happen if it was discovered the very company that justifies all this stuff for anti-piracy and the prices of its products by claiming piracy is the reason was found to have been the source of the leak? Every computer, hard drive, database, anything at all would be taken as evidence in the ensuing investigation and thus for all purposes shut down MS. They would then become the most infamous pirate of them all.
-
"Should we start a topic focusing on Vista compatible registry tweaks?" If you get me a list of the reg tweaks from nlite i'll be happy to check each one to see if they work in Vista, or provide changes for the existing ones to make them work in Vista if it can be done. A lot of reg tweaks that formerly worked in XP need either modifications to work in Vista or don't work at all because the facilities for them that were present in XP no longer exist in Vista. I'm already posting reg tweaks in the Vista Tweaks and Tips section I know work, might as well throw these into the mix because i'm already set up for testing reg tweaks. I don't use the product my self but i'd be happy to contribute by testing out the reg tweaks for you.
-
Sounds almost like bad drivers, but it could be a lot of things. "generic pnp to lcd flat panel 1280x768" I assume you do actually have an LCD display, are you sure the display is capable of 1280x768? And is the 1280x768 actually supported by the monitor? (try 1024x768 and see if that works). Do you by chance have the refresh rate set higher than the monitor can handle? (try the default of 60 hz and see if that works OK) Are the drivers your using actually for the Vista RTM? (try the in box Vista drivers and see if they work) A whole lot things it could be...but...since you mentioned re-installing, this time when it re-installs don't change anything just let what ever the defaults are for Vista install and don't change any drivers or anything. Then try to set the resolution on your monitor and try that out for a bit before adding drivers or anything. Oh yeah, a couple more things; make sure the connector for the monitor is firmly attached. Also, try uninstalling the video card in safe mode then reboot and let Vista re-detect the card.
-
Might be, but he said both the memory was the same manufactor, brand, and speed, and his score went down where as yours went up as might be expected.
-
Try this, disable the IPv6. Some routers can't deal with IPv6. I don't think Vista is your real issue, its just where your seeing the issue occur. Have you tried connecting straight to the internet without the router? Also remember the SPI in the Vista firewall also has a little issue with SP1. Try disabling the Vista firewall and connecting straight to the internet without the router. To disable IPv6, open up the properties of your connection and uncheck the IPv6.
-
hey! I've seen this one happen! It might be some of these general items you can check.... 1. Are you sure you equally populated the memory slots on the MB? (consult the MB manual) 2. Take a look in system and see if it says you have 2 GB. If it says you have 2 GB, try #1 again. 3. If # 1 doesn't solve the problem check your BIOS settings area concerning memory. 4. If # 1 - 3 doesn't yield a solution, check each stick of memory seperatly by booting on only one stick at a time. 5. If # 1 - 4 doesn't solve the problem, start to suspect that you got hold of a bad stick of RAM - it happens.
-
Your still using RC1. The last build available to the beta testers before RTM was RC2 build 5744. Your problems seem like the reduced functionaility sceinario because the OS failed activation or validation. Use a valid key and re-activate Vista. If you don't have a valid key then your out of luck. If you do have a valid key and have activated, have you manually modified or replaced any files (.dll, exe...etc...) that are native to Vista? I ask because manually modifying or replacing some files in Vista can cause validation failure which may allow a proper activation to occur but a validation to fail. You said "Now what has happened about a month ago"....thats about the 30 day limit without activation before the reduced functionality mode kicks in. A re-install is not going to solve the real problem for you if the problem is activation because 30 days after you re-install and haven't been able to activate the same things going to happen again. However, i really think that if you have a valid key that you have failed to activate, and if you do not have a valid key and have not been able to activate your experiencing the reduced functionaility mode due to lack of sucessful activation or validation (requires a valid key). Try re-activating.