LiquidSage

you can get a usb 2.0 wifi adapter...but if your looking for an excuse to buy an lcd....

there are a few different versions of ntfs 1.2, 3, 3.1. Win2000 does read/writes according to v.3. XP and 2003 uses v3.1. Anytime Win 2000 messes w/ your hd, xp/2003 will need to fix the files to conform to 3.1. Problems and possible damage to your data should be expected if you connect to win2000.

Start up is a critical folder. Windows even whines when you try to delete it in the start menu. Don't go overkill w/ your cleanup. Deleting as much as possible (even empty folders) can have a dramatic global effect just to save a few kb's and a few less files to look at.

It doesn't get any easier than the guides here. Learn windows and actually spend the time to read the guide before giving up. With all 10 builds of windows, you should be able to work something out

I've run into this issue on a client's computer. It's actually a fairly well known bug for people making Installshield wrappers. This mainly pops up when you switch common users and current user paths. Unhandled Exception 0x80040707 If your paths in the reg are correct but you did change the default locations in your unattended, try creating the actual folder through cmd lines or $OEM$ before executing the offending installer. Also, make sure you have proper permissions and 'read only' is off (Though I highly doubt that would be the cause if this is happening during an unattended.)

if your router is a linksys w/ speedbooster... then your wireless card will see some improvement in signal strength. That means higher speed. Now in reality, the speed increase is negligible. With or without SpeedBooster you will be luck to see any better than 40mbps. With physical obstacles and other factors involved such as the extra overhead for security and other wifi cards, you won't see much, if any difference. If you feel like spending the $$.... just get a combo a/b/g card. Remember, Speedbooster cards only work with speedbooster ap's and routers. Your effort would be better spent in moddin your antenna for better signal and or improving the general conditions that affect wifi signal strength.

If it's old or new.... Hardware: check if the cables are in all the way. Check the ram w/ memtest or something similar. check w/ your hand, the heatsink for your cpu and gfx for really hot temp. Buy a can of air and dust it while you are in there. Software: Need more info about system. Network lags can freeze a computer...esp true in business setups. Grab something like Iolo's system mechanic and do a junk file cleanup, registry optimization, and Internet optimization. Uninstall all useless programs to narrow down or eliminate the offender. Last but not least....Full scan for spyware/adware/viruses (this is probably the problem if it's a software issue since we all love to abuse the Internet.....as long as it's not on our own work computer).

you can always gp to OSH or a hardware store and buy a piece of really thin rubber foam to put behind the mobo

If the firmware update you downloaded is made with installshield, use WinPack to extract the files and with any luck...a simple r.click -->install on the inf file should do the trick

Good to hear you will be getting a replacement. I don't think longhorn is responsable. SmartDoctor or a sudden reboot / crash while the system was altering the bios would be more likely. Longhorn certainly didn't help the situation due to lack of driver support. An OS really doesn't change settings on a gfx card bios. The user, through software made to tweak the card does. RMA = Return Material Authorization

SP2 and it's enhanced security is the problem. To enable access to denied shares on a XP SP2 machine, make a reg file and merge this into that XP SP2's registry. the reg file to merge into XP SP2 registry.... ErdCommander should now be able to connect. This reg file does not need to be ran on any other OS version.

well....now it does sound like the card. if it's new enough, you may be able to RMA it. Yes, these days most mobo's do not need a vid card to boot. This may be too much but... Setup up Remote Desktop in WinXP for a user w/ full access. Make sure XP boots up by default. Swap cards and go to a different computer on your network (use a crossover cable if you don't have a network). From there, log in aand see if you can then mess with either the ati card's display settings or the installer for SmartDoctor. Hopefully that will work. Other option: if the riva gfx card is PCI based, Have both cards hooked up to your comp and set PCI display in the BIOS. When XP boots go into device manager and see if the ati card is detected. Then open display properties and make the ati card a secondary display device ( you will need to have one of the outputs on the card hooked up) You should then be able to mess with ati settings or SmartDoctor. Since this problem shows itself from BIOS --> OS, you will most likely RMA'ng it or returning it for a refund. If you do, go get a 9800 256mb SE version. Most can be succesfully hard modded to 9800XT. I've done several for people i know and have not had any probs, It probably cost less than even a 9600xt these days and you will have new features not found in 9600. I have heard mixed comments about ASUS's twist with ati chips. Good luck!

try putting all files in uppercase

it's sounds lke a software problem so far. try just basic MS cert ati drivers through your hardware profile properties. You may just have to live with it for now since you are using longhorn. A good way to test is to make a basic bart pe /win pe disk and see if it has the same no vid issue. also, if you have more than just a monitor hooked up , check that it is not switching to secondary device. If you have an on board graphics card, check to see that your computer isn't switching those as well. it couldn't hurt to reset the bios and put all settings to normal. do you oc your card or have done the soft/hard mod to make it XT?

there are 4 files that are directly affected by changes in setupp.ini for winxp and I'm pretty sure the specifics of such files will not be of suitable discussion on this board. 270 will work for win2k but has little relevance for xp unless you have the proper file set to match the pid change. Rayza.... if you go to a more stable win2k SP3 or Sp4 build, you will not run into any more prompt problems than you would normally on win2k. From what your concern is, I must again urge you to check that you are not trying to invoke an upgrade instead of a new install. More than likely your XP has different keys for New and Upgrade installs. This is not uncommon. Plus, keep in mind that 'gosh's method' applies to new installs.

http://support.microsoft.com/default.aspx?...Ben-us%3B303013 will explain why you can't see more than 137 gigs. 48 LBA is not enabled by default. If you ever reinstall windows it must be XP SP1 or better with this setting enabled or you could have integrity problems with the partition. That said, it is much safer to divide your hd into a few partitions that are around 120 gigs so win2k SP3 / winxp sp1 and above can see them w/o any special considerations. An easy fix should be found at the hd maker's site via a utility that will enable you to activate 48 LBA mode. A quick one to use would be Maxtor's LBA fix found in utility downloads or 48bit check tool. 3rd party partition prog's that can work with your entire HD regardless of LBA setting that i know of: Acronis Disk Director Acronis Partition Expert Paragon HD Manager Power Quest Partition Magic Your board CMOS error could be many things.Considering you did a BIOS update, it would not be surprising to see that. Anything from wrong date time to changed IRQ or power management setting could cause it. If you had your board OC'd through the BIOS and then updated, that could cause it as well. For what you did, just ignore it unless it keeps popping up.

your hex viewer needs to be reinstalled (what dll is missing?) hexworkshop or free xvi32 v2.51 work very well. Obviously you need to check your additional install files. I would start with the drivers and then add software to see where the culprit is. Probably the drivers. You mention win 98 in your post are you trying to install to a fat32 or ntfs partition? BSOD can occur installing to a fat32 disk with pre win2000 OS already installed.

Not to ask the obvious but, why would you try to make this project in virtual pc running a non sp version of 2k? Talk about making it hard on yourself! It matters very little if the setupp.ini is changed for without valid corp files, you will always run into probs. with keys & activation at some point. Setupp.ini lost it's magic after Win2k. If your key and xp corp build are genuine, make sure not to d/l updated setup files and make sure you are not trying to run an upgrade instead of a clean install. If you are set on doing this in a virtual pc and your unattended is a full build of XP (hopefully not altered past a basic winnt.sif file), make a new virtual machine w/ a new virtual HD. Begin to install your unattended XP distro. When setup finishes copying files and asks to reboot, shut down the machine and mount the disk as a secondary HD on your virtual win2k machine and then copy the files.

right now, you can probably find 2 hd's ~200-250gigs for about the same price as 1 300gig if you look hard enough and a decent ide controller card can be found for as little as $15. (I myself found a sil680 for $20 and love it) That means more space, faster access across 2 seperate disks and only half the depression when you start the computer one day only to find your disk is dead along with everything on it.

either that or it is a full-frame uncompressed avi which is easy enough to change into compressed avi or mpeg (probably a bit faster too).

http://tech-hints.com

DOSBox

loader.bin in the boot folder is a file included with cdshell. it triggers the menu. From there, your menu selection choice will trigger the proper xxxx.bin file that points to the loc. of whatever OS your are installing.

was this before or after install symantec AV and CS? Features like script blocking and having AV scan levels too high may be blocking you from running ussf. (Solution : ditch Symantec and get similar products that don't cause more problems than they are supposed to fix)

mic has been standard for a longtime on mobo's (it is the red circle) i would just like to add.... 1st don't be stingy on the quality of your mic even if you don't plan to use it often. if you use something like phone over the internet and esp. voice dictation / cmd software like Dragon Naturally Speaking then you really should be looking at high quality mic $75 and up. Putting out $20 on a mic is like getting the $50 car paint job deal. Everyone will notice!. Mic's are really one of those items where you get a good one, or just don't even bother with it. 2nd make sure you keep your speakers low / off and the rec volume a notch or 2 below max when recording. I also try to keep the mic line far from power cables as well.