HorseloverFat

Member
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About HorseloverFat

  • Birthday 01/12/1982

Contact Methods

  • Website URL
    http://
  1. Called MSI just now, and you were right - it just doens't support dual displays, except cloned (and even then, like I said, the cloned dual display was dimmer and glitchy, so generally undesirable). But yeah, the card just doesn't allow me to extend my desktop over both. Thanks for your help!
  2. Thanks for your reply. Hmm, that thought had crossed my mind too, as a sort of "worst case scenario". I'm going to contact MSI tomorrow (their tech line isn't open on Sundays) and ask them about that. The thing is though, this card was running 2 displays for ages in another computer, with the VGA out and the TV out. But I guess that doesn't say anything about whether or not the VGA and DVI outs can be used simultaneously... I guess I just assumed that if it was capable of doing those at once it'd be capable of doing the other two at once. Anyway, here's hoping that MSI tells me that's NOT the case, and that it's just some little box I need to check off somewhere. Heh.
  3. Hello, having a problem and wondering if anyone can help. I'm trying to set up a computer with an MSI Radeon x300SE 128mb video card and XP Pro SP2. I have 2 Viewsonic CRT monitors connected (one 19" and one 17") and I'm trying to get dual display set up. Every other time I've set up a computer with a dual out video card it has just worked, but this time it is not. Here's the details: When both monitors are connected and turned on they both show the same thing, and they're also both dimmer than they are if only one is conencted, and they're a little "glitchy" when both are connected, but not when it's just one. I see only one monitor listed in the Device Manager. I've tried changed the cables around, I've tried doing one at a time, and still I only see a single Default Monitor in s Device Manager. I can update the drivers for it to those for either of the Viewsonic displays, but that doesn't accomplish anything except getting Device Manager to say the proper name of one of the monitors - I still only see ONE. In the Settings tab of the Display Properties window, I see two monitors, one of which is greyed out. I can't choose to extend my desktop to that monitor, when I click apply the checkmark just goes away and it remains greyed out. I read on another site that someone managed to solve this sort of problem by enabling the second display vide the ATI Catalyst Control Center, so I installed that and gave it a try but I can't extend my desktop from there either. In Googling this problem I also found another forum where someone suggested turning down the resolution to make sure it's not a matter of the video card not being able to handle that many total pixels, so I tried that and no luck. I think that pretty much sums up all the pertinent details. So, has anyone experienced something similar, or have any ideas about how to get both displays working?
  4. Cluberti: Thank you for the link and for taking the time to have a look at the dumps. I share your suspicions about the NVidia driver since, as I said, I'm pretty sure the problem started around the same time I switched from the Marvell LAN to the NVidia. I initially did so because I couldn't get wake-on-lan to work with the Marvell LAN, but now I've got it working so there's no reason to stick with the other LAN if it is indeed responsible for the crash. I'm going to re-enable the NVidia LAN in the BIOS so I can uninstall it, and then disable it in the BIOS again, and see if that fixes things. I'm also toying with the idea of just switching to uTorrent and hoping that fixes it. PS. I could give you a full dump, but it's 512mb and thus impossible to upload here. Heh. JuMz: On my system, Windows just puts the dumps in C:\WINDOWS\Minidump\ but I'm not sure if I had to enable something to get it to store them there. I don't *think* I did, so your's probably puts them there by default too.
  5. Thanks for your reply. Yes, I did patch TCPIP.SYS, but I already thought that might be the cause of the problem and reverted it back to the original backup file to test, and still it crashes. Plus I've been using BitComet for a long time and right around when I first started using it I started patching TCPIP.SYS, and this problem didn't start until recently.
  6. Wondering if anyone could take a look at some minidumps and help sort out a persistent BSOD problem I've been having. Lately I've been experiencing semi-regular BSOD crashes on one of my computers. It's an extremely mediocre setup (Sempron 2400+, 512mb, etc) that I use solely for running some P2P clients, so I don't have to waste resources on my other computer or leave it on constantly. I should also mention that it's running XP Pro with SP2. Anyway, back to the issue. Maybe 4-5 times a day I've been getting a blue screen of death. It used to just reboot, until I changed the "automatically restart" option in the hopes of getting some more info to try to solve the issue. The blue screen mentions TCPIP.SYS and some memory addresses, but aside from that doesn't give much of a clue as to what's going on. I *think* the problem is related to BitComet, as it always seems to happen when that app is running. I've turned off most of my other apps and the problem still occurs. Tonight I'm going to try running the computer with everything I usually have running EXCEPT for BitComet and see if the problem still happens. When this first started, after Googling the "Your System has Recovered from a Serious Error" message that I initially was getting after an auto-reboot, I thought it might be bad RAM, so I ran MEMTEST and sure enough there were errors, so I replaced that right away. MEMTEST no longer finds errors in the RAM, but the problem persists, unchanged. Then I got to thinking about what had changed recently that might be a factor, and thought that the problem might have begun when I switched from my motherboard's onboard Marvell LAN to the onboard NVidia LAN, so I switched back and disabled the NVidia LAN in the BIOS, but no luck there either (although it did seem to reduce the frequency of the crashes - maybe a coincidence, maybe not). I know for sure that it's not malware or a virus, as I've had Kaspersky Internet Security Suite running real-time protection and I've done a full scan on the highest protection settings. I also should mention that I did a fresh format very recently, installed all Windows updates, etc. Oh and, the problem DID exist before the format, I was hoping it would get rid of it. I haven't completely ruled out the NVidia LAN as the culprit, since even though it's disabled in the BIOS the drivers would still be installed, would they not? Right now that's my only lead, since the problem did seem to start when I switched to that onboard LAN. Aside from that there's nothing I can think of except a hardware failure of some sort, and I've already ruled out the RAM by replacing it with a brand new stick. I've also been running ASUS' PC Probe utility to monitor my power supply, CPU/Motherboard temperature, etc. and it hasn't popped up any warnings. Sorry this post is so long, but I always prefer to err on the side of too much detail than not enough. So, can anyone suggest anything, or gather any clues from the minidumps? I'd be eternally grateful for any help. Aug11Dumps.zip Aug12Dumps.zip Aug13Dumps.zip
  7. Umm, because I've been trying to find it on Google already without any success? Do you really think that I would wait for a response to something in a forum without attempting to find it on Google first?Correct me if I'm wrong, but is this or is this not a Software Discussion and SUPPORT forum? I was under the impression that this was an appropriate place to ask questions of this nature. It's not like I've flooded the board with new topics or anything, either - this is my second thread in this forum. If my threads annoy you for some reason, feel free to not read them.
  8. Hello again, I have another question about sharing folders via the command line... Is it possible to enable file sharing in general via the command line, or, failing that, with a registry edit? I'm trying to design a batch script that will share a drive on my computer automatically, which will be run on first logon during an unattended installation. The problem is, when I share the drive via Net Share in the batch file, the drive appears to be shared, it has the hand below the icon, but remote computers can't connect to the local computer at all until I go to Sharing and Security for the shared drive and click the "I understand the risks but blah blah blah enable file sharing" option. So, I'm just wondering if there's a command or reg edit that will take care of this for me. Thanks!
  9. Hmm, I could have sword that NET SHARE wasn't allowing access to the subfolders... When I share a drive or folder the "typical" way (right-clicking and choosing Sharing and Security) it takes a bit of time, saying "Setting Folder Permissions" but NET SHARE applies the share settings immediately, which lead me to think that it was just applying the settings to the root folder. Also, the "typical" method works fine and provides access to everything within the folder. Does sharing with that method change the NTFS permissions automatically or something? I will look into that permissions command that you mentioned though, thank you.
  10. Hi, I just have a quick question that hopefully someone can help me out with... Using the NET SHARE command, is it possible to share a folder on the network AND share all subfolders within that folder too? For example... When I type net share name=C:\Shared Folder\ it typically shares the folder "Shared Folder" but it wouldn't share "Shared Folder\Subfolder". Is there some option for the NET SHARE command that would make it share subfolders too, or is there an alternate way of doing this via the command line? Thanks!
  11. Hello. I'm new to this forum, and just started learning about how to do an unattended setup. Using the boot from CD with WINNT.SIF on a floppy disk method, and I'm having a few minor problems: 1. My keyboard layout settings aren't working. In the winnt.sif reference page here on this website, it says that "by setting your Keyboard Layout, this prevents the Language icon appearing on the taskbar when you've logged on." However, I have my keyboard layout set up as per the instructions in my answer file, and not only does it still display the language icon in the taskbar when I first log on, it also defaults to the WRONG keyboard layout (US). The keyboard layout specified in my answer file (which I'll paste below) is "Canadian English (Multilingual)" but when setup completes and I get into Windows for the first time, I see the EN icon of the language bar, and next to it a keyboard icon. When I select the keyboard icon I see the options US, Canadian Multilingual Standard, and English (Canada), and by default it is set to US. I don't understand why this is happening, as I've set up my answer file exactly as all of the instructions I've read specified. I should also mention that the LANGUAGE options from my answer file install perfectly, just not the keyboard layout. 2. The other problem is a bit simpler - my display settings are not taking effect. When the installation procedure is finished and windows starts it still prompts me to change my resolution, and when I hit okay it defaults to the usual 800x600. 3. The workgroup I specify isn't taking effect (ie. when I go into the properties of My Computer after setup completes it is still set to the default WORKGROUP). I think the reason for this, however, is simply that the XP CD doesn't contain drivers for my ethernet controller and thus doesn't prompt for network settings during installtion. Once I get the basics of this unattended setup business under my belt I plan on integrating some OEM drivers into my XP CD to take care of that, but I would just like to ask, in the meantime, if I'm on the right track - ie. would adding OEM drivers solve this issue, and allow my answer file to change the workgroup? 4. One last, very trivial question - I created my WINNT.SIF file using setupmgr.exe and I'm sort of curious why it put quotes around some of the values (MsDosInitiated="0" and UnattendedInstall="Yes") and not others? When adding additional keys that setupmgr.exe didn't create, I left the quotes off. Should I remove the quotes that it added, or should I add quotes to my own entries, or does this just not matter? These should, I imagine, be easy for you guys to figure out, since they seem pretty much like entry-level issues. Thanks in advance for any help you can provide. Here's my WINNT.SIF as well, so you can see exactly what I'm doing: ;SetupMgrTag [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=No TargetPath=\WINDOWS KeyboardLayout="Canadian English (Multilingual)" Repartition=No UnattendSwitch=No WaitForReboot=No [GuiUnattended] AdminPassword=* EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=35 OemSkipWelcome=1 [userData] ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX FullName="Matt Stata" OrgName="" ComputerName=MS1 [Display] BitsPerPel=16 Xresolution=1024 YResolution=768 [Components] Msnexplr=Off Charmap=On Rec=Off Fax=On WMAccess=Off Msmsgs=Off OEAccess=Off Pinball=Off Freecell=Off Hearts=Off Zonegames=Off Minesweeper=On Solitaire=On Spider=Off [RegionalSettings] LanguageGroup=1 Language=00001009 [identification] JoinWorkgroup=FEDERATION [Networking] InstallDefaultComponents=Yes