|
Hrm how much room is it supposed to take up? I read that the recommended partition size was 16gb or so so I gave it 30 because I like to install applications that wouldn't survive a format anyway in the same partition as windows and keep my storage drives free for other stuff. XP had 20 gigs free of its 30GB partition with all sorts of applications installed. I installed Firefox and my IM client and such in 7 and it's already up to 23GB used, yikes. And system restore claims it's only using 180MB of that? I'm pretty happy so far though. I only used Vista on a laptop that really really really should not have come with Vista (1GB of RAM does not a good Vista experience make...) so even the Vista features are new and shiny to me. The amusing part is that things which didn't work in XP64 are working fine in 7... it's sad that RC software has better compatibility than XP64.
|
| # ¿ Jun 1, 2009 00:56 |
|
|
|
| # ¿ May 24, 2013 10:12 |
|
|
Stupid newbie question of the day. Can I run things pinned to the taskbar as Administrator? I had the launcher for WoW pinned there but in order to actually patch through it I had to go fish it out of the folder to run as Admin. I couldn't find a way to run as admin off the pin, or pin it as an admin icon... but that doesn't mean I'm not just  [edit] I knew if I posted this I would figure it out immediately! Right click on the menu you get AFTER right clicking the first time, and the admin action is available. This has been your moment of the day. enjoy.
Tagra fucked around with this message at Jun 2, 2009 around 22:24 |
| # ¿ Jun 2, 2009 22:20 |
|
|
free bowl of soup posted:I let it sit once for 15-20 minutes before I gave up. For what it's worth, mine (x64 7100 RC) did this as well with no USB devices plugged in. I let it sit there on the blue screen for 20-30 minutes, worrying the whole time whether it was actually going to work or not, and then poof it says welcome to windows and the rest was flawless. And as a bonus, Vista x64 did the exact same thing when we installed it on the other computer... except in that case they were too impatient and reset it, then booted the installer off the disk inside of XP. When the computer rebooted it went straight into setup instead of hanging on the blue screen.
|
| # ¿ Jun 7, 2009 05:08 |
|
|
Does Win7 use a different "Windows Experience" rating system than Vista? We built two computers with identical parts. One has Vista x64 and the other has Win7 x64 7100 RC. Vista rates everything at ~5.8. Win7 rates everything at ~7.9 except for the hard drive, which it rates at 5.8. Zuh? Not that the "Windows Experience" is anything to swear by, but I'm curious about the difference. Does Win7 rate things differently or is it an indicator of things running better under 7? Or is the one computer screwed up and we need to fix its performance 
|
| # ¿ Jun 8, 2009 09:30 |
|
|
This is pretty minor and probably more of an inexperienced with administrator rights thing, but maybe someone can help... I run TVersity to stream to the Xbox360, and on XP all I had to do was set it to share on windows startup, and it was good to go. On 7 however, when the system is rebooted, the media server launches, but it is apparently not launching as Admin so the Xbox is not able to access anything until I open it as admin and restart the server. Is there any way to get it to launch and share as admin by default?
|
| # ¿ Jun 19, 2009 07:27 |
|
|
NoArmedMan posted:I'm not going to be able to help you here, but I have the same setup and it works with no problems. On a previous release though I had a similar problem and never worked it quite out. I did find this guide: http://www.pcmag.com/article2/0,281...3129TX1K0000625 But I haven't tried it yet. I'm only assuming the admin permission is what's causing the problem... I don't have the problem it states in the article where it nags for permission every bootup, the program boots up just fine but the Xbox is not able to connect to the share (but it can see it) until I restart it with admin priviledges.
|
| # ¿ Jun 20, 2009 20:56 |
|
|
Small posted:Anyone interested, or does this just only bug me? If anyone wants it I will try to polish it up... if not, I'll just use it myself. That bothered me too, but I turned off merging completely and have been happier with it that way. I guess I just like being able to glance down and see everything seperately, but I don't generally have a million things running either.
|
| # ¿ Jun 21, 2009 19:17 |
|
|
Anonononomous posted:Yeah, that's already at full and it's not picking me up. I know the mic isn't broken because it works just fine in XP. Which sound card do you have, and which drivers is Win7 using for it?
|
| # ¿ Jun 24, 2009 23:52 |
|
|
WTFBEES posted:My 64 bit install (which MS says requires 20GB) only took 15GB or so. Alright, I think I need some help. I made a 30gb partition on my drive for the x64 RC, because it was supposed to only take 15. So I figured 20 for windows and a whole 10gb to install whatever little applications that I was going to nuke when I formatted it anyway. After install of windows, it said 25g were used already. I poked around and system restore only claimed to be using a few hundred mb, I cleaned out system files and whatnot, and couldn't really reclaim any of it, so I just left it alone figuring "oh well". I just looked now and I'm down to 1.8GB free.  where is it going?I poked through the public folders since things like WoW like to drop their goddamn patch files there even though they're on other drives, but it's all clean... I DO have 8GB of RAM which might explain some of it if there's a hibernate file somewhere sucking it all up, but I disabled hibernate and a search for "hib" only brings up the power options in control panel, no hibernate related files that I could find. Where can I look to find my space? Tagra fucked around with this message at Jun 28, 2009 around 05:48 |
| # ¿ Jun 28, 2009 05:42 |
|
|
Ziir posted:Disabling hibernation didn't free up any space until I ran it from the command line.  8GB free. Thank you!I also discovered where some of the rest of it went... apparently my TVersity media server is saving the files shared onto C despite my shared servers being on E. I'll have to see if I can beat it into submission. [edit]ohhh those are its temporary files from transcoding. I just told it not to use so much space so it will delete them after it's done. Goddamn that was almost another 8GB sucked up right there since it also set it to the RAM amount 
Tagra fucked around with this message at Jun 28, 2009 around 05:59 |
| # ¿ Jun 28, 2009 05:54 |
|
|
I installed the RC back in May and had my very first crash today. I'm still running 7100 because I'm lazy, and I'm not worried about it since I'll be updating to the proper version as soon as the University gets it, but I'm just curious if it was a common thing that's been fixed in later builds or if I broke something or what. I went to open windows explorer and the list to the left only had "Libraries" with a magnifying glass spinning over it. No computer, no subfolders, nothing. My library folders were there, and if I right clicked explorer on the bar the jump list was there and they all opened correctly (except that the list on the left was still empty), but if I went to "computer" from any of those folders, it would lead to a blank screen and the loading bar up top would fill up and then just sit there. I opened control panel to go look at the event viewer, and it turned out that was blank too. I could access any control panel command by searching for it in the start button, but the panel itself was blank. Nothing that wasn't fixed by a reboot, and it was probably some kind of explorer problem that I could have fixed by stopping and restarting explorer even, but I'm curious if it's common or if I did some arcane action that caused it to break. Interestingly enough, googling for 'blank control panel' brought up a lot of hits for Vista... The last four days of event log are full of "The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations." I don't actually know what that means, but I'm assuming it's somehow related. I am running TVersity as a media server for the Xbox, I don't know if that's the server it's referring to or not. RAM usage seemed normal though. My system uptime was just over 40 days, so I guess it was due for a reboot anyway 
|
| # ¿ Jul 27, 2009 08:57 |
|
|
stedd posted:You most likely have a bad driver that's leaking nonpaged memory. You can read a little more about nonpaged vs. paged memory here: http://blogs.technet.com/markrussin...26/3211216.aspx It appears to be /Devices/LanmanServer that threw the errors, approximately once every 10 minutes starting on the 24th, but I'm guessing that doesn't necessarily mean it's the actual device that caused the leak? Just that it was the first one to run out of memory? Is there a way in just the base Task Manager to see which process might be leaking, or do I have to go get the program talked about in that article? It still took it a month and a half to crash, and when I go to the final version I'll be updating everything again, but now I'm curious to see which one is loving up.
|
| # ¿ Jul 27, 2009 17:26 |
|
|
Blech. Maybe this should go into HOTS but it's Win7... How can I track down a buggy driver? I think I have one somewhere and it might be causing issues. I posted here before about the weird memory problems in the event log and since then I've been having some lock-up issues. I just ran windows update and let it change any driver it saw fit, one of them was my display driver (nVidia - I've been running 185 since I installed Win7 with no real issues, and it updated to 186 even though I know I just installed 190 on a different machine...) and one of them WAS my printer driver (Canon ip2000) which was recently installed prior to the issues. I'm hoping that was it, but without any sort of event log entries I have no idea how to know. Other than if it stops crashing now that it's been updated. Usually it's just the explorer stops responding and slowly dies until everything is unresponsive and I have to reboot, but this last time I had just come back from a boot, went to search for something in Firefox and closed the window and bam - hard lock. No cursor movement or anything that time. I'm starting to worry it might be a hardware issue . Temps are perfectly fine at point of lock in RealTemp though, it's not overheating.
|
| # ¿ Aug 5, 2009 21:27 |
|
|
-Dethstryk- posted:On an 8800 GTS, I can't run WoW in a maximized window. The framerate drops significantly and stutters regularly. I have to just play in full-screen mode, where it runs beautifully except for when it just starts crashing with graphical glitches. Hmm. I haven't had graphical glitching but I've been having lock-up issues with WoW in 7 (just the 7100RC so I'm curious if later builds are better, too) I was wondering if it was a driver thing or a memory thing or what. I'm positive it isn't a hardware issue, because my husbands motherboard committed suicide so we hacked together an old computer with the 7100RC for him while we wait for the RMA to return, and now HE is having the same lock-ups, and without any addons or anything installed either. Now I'm curious if anyone else here is having something similar. It's so intermittant it's hard to track down. Ever since installing 7 I've noticed loading screens cause the game window to flag as Not Responding, but it always loads anyway. I wonder if that's related at all. Primarily it will lock when zoning into Dalaran (either freshly logging on or flying into the zone from elsewhere, which is fun because you log back in without a mount or a parachute and splatter), and in battlegrounds or arena (also an exciting time to randomly crash!). Your character loads, you go to move and... frozen and Not Responding. The window will close instantly when we close it and we can log back in right away. I've only had it happen once ever on a raid and my entire system shut down that time (explorer went non-responsive), so it could be an unrelated crash because I had a bad driver leaking memory at one point too. The only thing in common between the two computers we've been running it on are that it's a 7100 build of the Win7 RC and they both have nVidia cards and drivers (a 9800GTX+ running the 186 drivers, and a 7900GS running the 190 drivers). I ran the repair tool to nuke all the caches and it didn't seem to change anything. At this point I'm just sort of hoping it's a driver that's having an argument with the 7100 build, and when I get my full version through the University next month it won't be an issue anymore, but I'm curious if it's a common problem.
|
| # ¿ Aug 10, 2009 23:44 |
|
|
I had nothing but trouble with RealTek drivers so I just let Windows install whatever the hell it thought was best, which was some generic HD audio driver, and I've been happiest with that so far. My only issue is that my microphone volume is extremely low even at max and micboost on, but it was like that WITH the drivers too.
|
| # ¿ Aug 13, 2009 20:12 |
|
|
Here's your Dumb Question of the Day. Dual-booting the RC was my first experience with both dual booting and creating partitions outside of the windows install process and even though it was easy enough, I'm still not entirely sure I know what I'm doing. My drive is set up with a big partition of stuff I don't want to format between windows installs and windows XP on it's own partition, and I created a new partition for 7 when I dual-booted the RC. In my understanding, even though 7 designated its partition as "C", my boot information is in the original XP partition, right?I'm about to get the final version of 7 off of MSDNAA and I'm wondering what the easiest most painless way of doing this will be, because I also want to reclaim the extra partition I made when I dual-booted. Is it easiest to: - Go straight to installing 7 and gently caress with trying to merge the partitions during the install process? (I know it had a partition manager but I don't know how powerful it is) - Delete the XP partition and merge it before trying to install? (if the boot info is there it makes this more difficult, right?) - Go straight to installing 7 in the RC partition and try to merge partitions after install? - Go straight to installing 7 in the XP partition and then merge the RC partition after install? - Something else that would be much simpler and you're horrified that I think this is so complicated? I'm currently leaning toward installing in the XP partition and then nuking the RC once I have the full version running... if the boot info is in that partition would it be the route with the least number of potential issues? If I install it in the XP partition which has been re-written to be D, will my new 7 install set itself to be C?
|
| # ¿ Aug 13, 2009 21:50 |
|
|
Xenomorph posted:The one Windows auto-installs works "ok", but I don't have full control over all the sound devices. Yeah you lose a lot of the fancy controls, but for me I never used anything but lovely speakers and the occasional headphones, so it was sufficient... it bothered me that the RealTek drivers greyed out all the controls when I was attempting to boost the volume on the mic, too. Since you use a RealTek with WoW, have you ever had problems with Vent? Using the RealTek drivers I had terrible problems with people complaining my voice came across vent with a "robot" mechanized sound and they couldn't understand anything. With the default drivers I only have an issue where if the volume is set too loud, it fades into static on their end, and since my volume is so low by default everyone is cranking it up on me and then bitching about static.
|
| # ¿ Aug 14, 2009 16:50 |
|
|
Xaranx posted:Dammit, I had xp on one hard drive, installed 7 on a separate hard drive, now I can't format the XP hard drive to use it for storage. I remove the hard drive physically 7 won't boot. That's loving retarded. Why would an installation of one operating system on a hard drive put critical information on another. I probably shouldn't even respond since I was asking about this on like, a couple pages ago, so obviously I'm no expert... but what's happened is 7 used the existing boot information (on the XP drive) and modified it. So it won't let you format XP because that would kill the boot information, and when you physically remove XP (and the boot info), it doesn't know how to boot. As far as I can tell, this is very simple to fix because your 7 install disk will go "oh poo poo there's no boot information" and replace it for you. So either format XP using something other than windows that doesn't care where your boot information is, or remove the XP drive and pop in the 7 disk and see if you can get it to write the boot info in. [edit] Yeah what that guy says \/
|
| # ¿ Aug 17, 2009 23:11 |
|
|
I have a performance question. I installed the RC on a brand new high-end machine, but my husbands matching brand new high-end machine decided to commit suicide, so we hobbled together an older computer while we wait for the motherboard RMA to come back to us. I threw the x64 7100 RC on it because it was here and convenient and this is just temporary anyway so he can browse the internet and play WoW and bitch about how this computer lags more than his Quad Core machine with 8GB of RAM. The machine is about 6 years old and he was using it as a main machine up until we built the new ones a couple months ago: CPU: AMD 64 3000 Motherboard: A8N-E RAM: 2GB Graphics: nVidia 7900GS At first I was pretty impressed with how snappy 7 was on it, it felt better than XP used to. WoW is laggy as poo poo in the main cities and has terrible load times, but it didn't seem any worse than it used to be on those machines (it's totally bottle-necked by the CPU, nothing to be done) and is completely playable in raids, just like it was on XP. However, tonight he tried installing Vent on there so he could do some PvP in WoW, and Vent was so laggy he couldn't even transmit while WoW had focus. I don't understand why there was such a huge performance hit. We tried running Vent as admin and it didn't seem to help. WoW is pretty much maxing out the system, but it doesn't seem any worse than it used to be on XP and there was never a performance issue like this before. Does this sound like something 7 is doing that I can tweak somewhere, or does it sound more like the old computer having problems of its own? Hang in there buddy, they'll send the new motherboard back soon and then you can rest!
|
| # ¿ Aug 18, 2009 09:05 |
|
|
SpaceBum posted:This fixed my sound lagging problems w/ quake 3 on the 7100 build: God maybe I should take this to Haus... but I messed with it some more last night trying to get it to work. I tried a couple compatibility modes and he even messed around trying to give the program a higher processor thread priority or something (I didn't see what he did, that's just what he said he tried) and nothing changed. It seems to be that Vent is running, but the Push-To-Talk key is SO laggy that he has to hold it down for a good 3-4 seconds before vent registers that it's down. After that it transmits perfectly. But when you're in the middle of PvP or whatever, you can't sit around holding the drat button down waiting to yell at your teammates. Also if he leaves the mic open they'll hear him cursing at them, heh. When Vent has focus, it works perfectly. It just seems like it's not getting enough memory when it's not in focus, so the UI is laggy as gently caress. Is there an option in 7 somewhere to give more memory to the background programs, WITHOUT sucking memory away from WoW which is already hogging it all? They shipped the motherboard today so we should have his good computer back up within a week or so (god I hope everything loving works when we get that back) but I'd still like to see if I can solve this problem. Possibly related, the same computer has difficulty even running Flash. I know it's not a very powerful computer anymore, but really? I expect WoW to lag a certain amount but Flash? We never had issues like this on XP... is it because 7 is just harder to run on this hardware(doubtful from what I've heard) or is something buggered? Stats again were: AMD64 3000 A8N-E 2GB PC3200 RAM nVidia 7900GS
|
| # ¿ Aug 19, 2009 17:55 |
|
|
I have discovered that using Winkey+1 will open your first pinned program (or focus the window if it's already open), Winkey+2 the second... and so on. Which is pretty neat. Except that I keep re-discovering it while playing fast-paced online games trying to hit Ctrl-# hotkeys... I've pretty much solved it by pinning those programs up where I'm likely to hit the wrong keys, so that it re-focuses that window instead of trying to open a totally new program for me, but if anyone knows of a way to simply disable the feature it would be nice too. I poked through the taskbar menus but didn't see anything about shortcut hotkeys, hmm. I don't want to disable the winkey or ALL windows hotkeys, just that specific one :/ Tagra fucked around with this message at Aug 20, 2009 around 23:20 |
| # ¿ Aug 20, 2009 23:18 |
|
|
Bad Habit posted:I believe the Windows Experience Index rating thing is scheduled to run once a month at some time during the night. Check your scheduled tasks (type Task Scheduler into the start menu), you'll probably find it in there. Ohhhhhhhh... This happened to me too once and freaked me out because I was playing a game and the screen went black, then came back without Aero Glass. I was sure my graphics were loving up somehow, but I was in the middle of the game and it hadn't crashed so I just went "gently caress, I'll reboot after this" and a few minutes later it went back to glass and was fine. I bet it ran this on me. That's kinda dumb though, why do we need to update our Windows Experience Index at all if we didn't change any of the drat hardware? I had run it manually when I first installed 7 just to see what it said.
|
| # ¿ Sep 6, 2009 17:30 |
|
|
I haven't messed with it much yet so maybe it'll be something simple and I'll feel dumb. But anyway. I have a netbook running XP that I use for school stuff, and then my main desktop here which has the printer attached to it. Naturally, I write a lot of papers and other things that need to be printed out and carted off to the university. Tonight I tried to print something off my netbook for the first time since updating the desktop to Win7. The netbook sees the printer and then immediately says the drivers aren't compatible and it won't print. It's the exact same printer as before (a canon pixma ip2000), and XP still has the same drivers installed that it used to have, but since the printer is now running on drivers for 7, XP apparently refuses to touch it anymore. I mean, it's easy enough to just nab it over the network and print it from the desktop too, but is there a way I can make XP play nicely with the printer installed on 7?
|
| # ¿ Sep 30, 2009 05:20 |
|
|
jokrswild posted:I had a similar issue with Vista at first, but it turns out that that XP (32 bit) can't use Vista/7's 64 bit drivers, if that's the version you're running. You'll want to open up the printer properties, and under sharing (I think) click on additional drivers. You won't want to run the driver installation program from the manufacturer, you'll just need a folder with the 32 bit drivers inside to point to. Duh, I didn't even think about the fact that 7 is 64 bit and my netbook is still 32 bit... I think it still have the 32 bit XP drivers from before, but it's not recognizing it as the same printer so it's trying to install new ones. I'll try to make it see the XP drivers instead, even if I had to try installing it as local like Morphal suggests. Thanks for the help guys. I'm glad it wasn't something simple and dumb
|
| # ¿ Sep 30, 2009 16:46 |
|
|
Goddamn. I've been putting off installing my copy of professional since I had the RC all set up the way I want it and I'm a big pussy and was afraid I'd gently caress something up while the semester was still in progress and I had projects to hand in. But finals are done so I finally got off my rear end and installed it today. Most painless windows install ever. Within 10 minutes of hitting the desktop the only difference is that there isn't any "evaluation copy" text in the corner, and I didn't have to install a single driver. Even the video driver was the same one I was using on the RC. Which brings me to my question. I'm using a 9800GTX+, and I've been chugging along with some older drivers, 181 I think (I'd have to double check but it's in the 180s). I downloaded the latest drivers (I think 195.65 or something, again I'd have to double check but the latest as of today) but since Win7 automatically plugged in the same drivers I used to have (although it recommends to update them through win update, but I ignored that), and those were working fine on the RC, I didn't install them. I've been hearing murmurings of the 190+ drivers having problems. If these continue to work fine should I just sit on them for now? Anyone have a 9800GTX+ that can comment on the state of win7 drivers for it? [edit]Man I totally read the driver number wrong and it was much more recent than the 180s... I updated to 195.65 anyway for the hell of it, we'll see how it goes. Tagra fucked around with this message at Dec 16, 2009 around 02:00 |
| # ¿ Dec 16, 2009 00:00 |
|
|
Shofixti posted:Well I have a 8800GTS 512 and I had a lot of problems with the 190+ drivers. I was getting poor framerates in just about every game I tried. I had Vista on the exact same system with no problems at all with the same drivers. As I understand it, Vista & 7 have extremely similar driver architecture so I was a bit surprised by that. I eventually rolled back to 185.85 and it's been fine. Just one anecdote though 185 and 186 I think were the two which were most recommended when I did some quick searches, but a lot of people reported no problems with 195 either. My framerates seem normal with 195 so I'll see how it goes. I think 191 or 192 is the one they were suspecting of causing hardware failure in some cards which makes me , but several sites seemed to confirm it...
|
| # ¿ Dec 16, 2009 18:57 |
|
|
|
| # ¿ May 24, 2013 10:12 |
|
|
Oh man. I didn't have any annoyances with this running the RC, but now that I've updated to full version professional, all the folders I had while running the RC are flagged as belonging to someone else. This is fine, I know I need to take ownership of them and whatnot but... is there a way to do it all at once because going through a 1.5TB drive of poo poo and flagging each individual folder as belonging to me is kind of a bitch. Flagging the drive as belonging to me didn't change the stuff on it, and flagging a root folder isn't changing the folders inside of it. Am I just doing this wrong? [edit]NEVERMIND there is a checkbox to take control of subcontainers!
Tagra fucked around with this message at Dec 16, 2009 around 23:59 |
| # ¿ Dec 16, 2009 23:56 |
|
