|
So i did some registry hacking from support.microsoft.com, and rebooted the pc. It got up to the welcome screen, but then it stopped! 
So i first tried to do some hacking with the install cd, but nothing worked. That way i ended up reinstalling everything. And guess what? The drive letters are all ok now! The hard drive is just plain old C:, instead of some stupid I:.
Thank God that i didn't install anything! 
|
|
|
|
|
You can find this option in the administrator tools of windows.
I think the option is called "computer management" in the english windows version.
You will find a disk management page there where you can create/delete/format system partitions.
Select one of the partitions (or CD-roms, DVDs, ...) with the right mouse button and you will see an option to assign a new letter to that drive. You can also create more than one letter for a single drive or remove all letters with that option.
Don't try it, just do it! 
|
|
|
|
|
Thanks for the effort, but the problem was already solved (see 1 post up).
In the diskmanagement you can change drive letters, but not of the system partition, and that is what i want to do.
But thanks anyway! 
|
|
|
|
|
you cannot change the letter of the partition where the system is installed...
i had the same problem (Windows was supposed to install on C:, but it did on H: just because i had some peripherals connected).
i just disconnected the other HDD and reinstalled windows.
i think you're not obliged to disconnect the hard disk which contains other partitions ; fdisk might provide a function to de-activate a partition...
TOXCCT >>> GEII power
[toxcct][VisualCalc]
|
|
|
|
|
You can change the drive letter of the system partition, but then you will probably f*** windows up. I found an article that showed how to do it. With the help of that article i did some tweaking in the registry. windows started fine, until i clicked on a user, then it hung. maybe i had to change some system variables too, i don't know.
Anyhoo, windows got stuck, so i reinstalled windows just like you. I disconnected that stupid cardreader, and everything worked fine! 
|
|
|
|
|
Today, for no apparent reason, I am unable to connect to the network using the onboard network port on my PC. I have tried plugging another machine in by just unplugging that machine and plugging the cable straight into the new one and it works fine, so the problem seems to be with the computer not the network or hardware.
When I plug the cable into the computer it lights up green and starts flashing like it normally does when it was working.
In Windows, the status reads "network cable unplugged" but if I disable and then enable the adapter it flashes up as "acquiring network address" for a split second before returning to the previous message.
Any ideas? Can I test something? Change something? Does this sound like the port on my computer has suddenly died? Any help would be appreciated... I don't have the space to isntall a PCI NIC as all the slots are in use, and I would rather not have to replace the whole damned motherboard for a $1 component.
|
|
|
|
|
Check to see if the nic was disabled in the bios. Then reset settings for the bios and check that. After that check to see if there is a bios settings reset jumper on the motherboard. Also, you might want to test it with a minimum of extra cards plugged in.
Another common culprit is windows update "upgrading" drivers.
I can imagine the sinking feeling one would have after ordering my book,
only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
|
|
|
|
|
I shall check out the bios and give what you've said a try. I dont think it would be WU though as it hasnt downlaoded anything in a about week and the NIC was working this morning.
|
|
|
|
|
I tried everything you suggested, and played with a couple mroe settings I found, but nothing seemed to help. I installed a PCI NIC in place of the PCI WiFi card for the time being.
|
|
|
|
|
That's the problem with the integrated devices. If they do fail, they are part of the motherboard.
Another possibility is that you have a network cable that is close to tolerence. In that situation you will get ittermitent connection, some NICs will work some won't and the ones that do work will have outages, but it sounds like the NIC probably failed.
Most "hardware" problems are really driver/software problems so you typically have to go much further out of your way to elminate software problems. Some of NIC companies had diagnostic applications that ran under DOS that might be able to give a more definite result, but like I said it's probably let out the magic smoke. At least they make motherboards with dual NICs these days.
I can imagine the sinking feeling one would have after ordering my book,
only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
|
|
|
|
|
I've spent so much time trying to get it working over this past week that now I'm prepared to just let it be. In the not too distant future the whole machine will need rebuilding anyway so I will cycle the motherboard round to a testing machine and then see if I can find some diagnostics software to run on it.
|
|
|
|
|
David Wulff wrote:
I would rather not have to replace the whole damned motherboard for a $1 component.
If it is dead, you can get USB network adapters, so if you have a spare USB port, you're back in business.
|
|
|
|
|
anyone has done such job?please give me some hint!Thanks a lot
please contact:
max_xiayi@hotmail.com
|
|
|
|
|
max_xiayi wrote:
anyone has done such job?please give me some hint!Thanks a lot
why would you want to? Same sound file two cards, are you trying to reach 14.2 sound or something? You can go up to 7.1 sound easily now so the question seems rather bizarre.
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
It is possible, but the application has to support it.
Don't try it, just do it! 
|
|
|
|
|
I need to write a little app that can detect when the system clock
gets adjusted. (within limits) In a perfect world, I guess Id like to
know what process does the adjustments, but that may be the subject to
some follow-on post.
Can anyone direct me to some thread here in TheCodeProject?
Basically, I need to access the system's TIMECLOCK (the one that is adjustable,
and shows me the time in the lower right corner). I also figure I need access
to the systems UPTIME CLOCK (that just humms along - regardless of whatever
time the TIMECLOCK says).
I *think* that what I want to do, is just do an infinite loop where I read
the SYSTEMCLOCK, compare it to the previous reading.
If its within the limits of time I *expect* to elapse, then all is good. I
just sleep another 1000ms or some such, and test again.
If I detect that somehow the clock has gone backwards, or jumped forward more
than say 1500 ms, then I want to append to some logfile that a time-adjustment
has occurred...
Can anyone give me some guidance on this? Is this a workable strategy?
(I ask because I dont really know what my 'sleep 1000ms' step will do if
the clock is adjusted during my sleep... basically, WILL I KNOW if a
time adjustment has taken place? (even if its a slight nudge forward or
backward). How does this work behind the curtain?
Free candy-bar to the guy (or gal) that puts me on the path to elightenment.
Thanks,
-Newbie Dave
AIM: KewlBean36
|
|
|
|
|
|
Hi all, Just wanna ask this.. I used Norton Utilities 2005 (Disk Doctor) and it keeps saying my Security Descriptors are not fixed. It tells me to Click the 'Fix Errors' and to enable Surface testing, which I did and restarted the system for it to fix it...
After half an hour plus of waiting, it gets done and when back in windows, using norton disk doctor again, it reports that the security descriptors are still not fixed... Anyone have any ideas..?
Why I did Disk doctor in the first place is my system tend to randomly reboot itself lately? Could this be the cause? thanz all..
|
|
|
|
|
Ever tried chkdsk/scandisk?
Don't try it, just do it!
|
|
|
|
|
Tried it, doesn't work.. read this from symantec's own site but the problem still there... hehe.. any idea what kind of errors this problem may or may not cause... thanz..
|
|
|
|
|
XP does the complete shutdown sequence and at the moment the computer should power down, the hard disk light goes on and remains on even though I don’t hear disk head movement. Using the power switch is no help, the computer remains on unless I unplug it. When I plug it back, the hard disk light goes on again and remains on. The computer starts normally when I hit the power switch.
Any idea?
Thanks
Hugo Migneron
|
|
|
|
|
If it's been doing this since you bought it, my thought would be that the indicator might've been connected to the mobo backwards. ALso in this case the HD light would be going out when in use instead of turning on. Beyond this I'm stumpted.
|
|
|
|
|
dan neely wrote:
If it's been doing this since you bought it
It started doing it a while after the computer was bought, so I guess it cannot be the HD indicator.
Thanks for your reply anyway!
Hugo Migneron
|
|
|
|
|
|
Yes I did scan for viruses and spywares and there were none. Just out of curiosity though, could a virus/spyware cause such a thing even if XP is closed at this point?
Hugo Migneron
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
