raskren

It depends on what kind of array we're talking about. RAID0 provides no redundancy so removing a drive from the array destroys the lot. With RAID1 you can remove one (sometimes more than one) drive and still have an exact duplicate on the other drive(s). While the disks are online, any changes you make to one are permanently mirrored on the other drive. So, you couldn't copy "My Documents" to only one drive and not have the other drive reflect the change.

A RAID array (no matter what configuration) will show up as one physical drive in Windows Setup. From there you can easily create multiple partitions if you need to. Are you sure you know how to set up a RAID array? What motherboard and hard drives do you have?

This forum seems to be the closest match for this topic... I was just curious to see if anyone here has used Windows XP Embedded. I am very unfamiliar with this sort of O/S...it appears that you are given a set of "shared code" (the actual source code) which has to be customized and compiled into an Embedded image to be installed to the target device. Anyone have any comments/experiences?

I don't know what you are all talking about switching to Firefox for as this doesn't seem to be a browser problem. There's got to be a background application that is constantly checking the date/time so it can expire its 30/60/90 day trial or whatever. The problem might be caused by Windows Time and your time setting being adjusted by a network time server. I'd run a comprehensive malware scanner and try and think of some "free trial" software you've installed/deleted recently.

Well you can instruct the BIOS where to look for a bootable device but that's really all. By telling the BIOS HDD-0 is bootable, doesn't make it bootable. I still think you configured the textmode driver incorrectly. Did you tell nLite that it is a textmode driver and not a regular PnP driver? I don't know exactly how nLite does its driver integration thing with textmode but manually, you would add a .sys file and possibly a .dll file to the i386 directory of your install CD and adding an entry to txtsetup.sif. You might want to scan this directory for the pertinent files.

NTFS is pretty much read-only with Linux. Linux can read and write to FAT 12/16/32 with ease. You should use NTFS with Windows XP.

There's no master/slave configuration with SATA drives so don't worry about it. [Exactly] when does the installation process go wrong? Do you receive any error messages? It sounds like the necessary drivers are configured as regular PnP drivers and not textmode drivers.

No, you can't make a JPG image "better" while keeping it a JPG. That is mathematically impossible. P.s. The matte color on your avatar is wrong, graphics master.

There's a few things that could be amiss here: Boot.ini is incorrect or missing - not sure if recovery console tools will fix this or not. The MBR is corrupt - fixmbr should repair this You're bios setting are incorrect - i.e. they're set to boot from HDD-1 when HDD-0 is the bootable device If you're good with DOS/Windows and feeling adventurous, you could put together a DOS boot floppy with NTFS support (assuming XP is on an NTFS drive). You could then verify your boot.ini settings and the presence of your NTLDR file. You could also do a "repair" installation of Windows if your CD contains the same Service Pack level as the installed one - if SP2 is on your computer then you could repair using an XP CD slipstreamed with SP2. The repair rebuilds the boot information, reinstalls hardware, and replaces any files in the target install location that differ from the CD.

There's a difference between scaling the video image up and increasing the FPS. In either case the computer is still guessing what goes where and you're still increasing the bitrate without a tangible increase in quality. And, unless you want to watch multi-gigabyte uncompressed AVI files, all this has to be codec'd again.

I'm not sure I understand your question. You say you want to increase video "resoultion" without "loosing" a lot of "resouliton." Hmmm... There's no way to interpolate video to a larger size without a severe reduction in quality. Doing so would increase the bitrate of the video stream (putting more strain on the hardware and software to play it) and you would need to re-compress a compressed video stream further reducing audio and video quality. Just watch it in full-screen mode. If you really want to (which you'll probably do anyways) you could try Adobe Premiere or the myriad of other expensive video editing tools.

You can pull the Windows flag (in vector format) out of a PDF from the MS site (search for PDF). There are also some logos and box shots on their press site.

chankya, There are ways of doing it, but they require defeating .NET security features and changing software PID's - I doubt either is allowed on this forum.

Holy s*** dude, are you really posting CD keys in here? Can you say "ban city?"

big poppa is right. Your path is wrong. You need to point to the chipset INF file(s) using a complete path assuming $OEM$\$1 is root. DO: Drivers\001_Chip;Drivers\002_Modem;\Drivers\003_Agp DON'T: \001_Chip;\002_Modem;\... You should also load chipset drivers as one of the very first items. Load them before AGP, SMbus, Ethernet, etc.

So problem solved?

You are all crazy. There is no discernable difference between the two. Server 2k3 is built on the Windows XP code it just has unnecessary services/themes/hardware accel turned off by default. If a piece of hardware is flaky its an improper install or poorly coded drivers, not the OS. Driver support is exactly the same in either OS. Now, what's this foolishness that Windows Xxx is making hardware run hotter? That's absolute BS. For typical usage Windows XP Pro SP2 is the better of the two. Why? Price! The OEM version can be had for a little over $100. For a "workstation" Windows XP Pro SP2 is the better of the two. Why? Price! And, XP Pro will run all of your "workstation" apps just as 2K3 will. They're both NT. Professionals don't need 2K3 to work on! Garbage! BS! Rant! Rant! Bottom line is, there's no reason to use Server 2003 unless you're actually running a file/web/ftp server with more than 10 clients. Otherwise you can get the same product for much less, its called Windows XP.

Yeah, this has nothing to do with an unattended installation. Step #1 Back up your data! You shouldn't be messing around with disk utilities if there's strange behaviour going on. Just back up critical stuff ASAP. If chkdsk says "the volume is dirty" then the dirty bit is stuck. Go to the command line and type "fsutil dirty query x:" where "x" is your drive letter It should say the volume is dirty or NOT dirty. If its dirty, then there might be something wrong with the drive. If its not dirty check your Scheduled Tasks.

So it looks like my stuff is getting "republished." Fine with me, thanks for the credit.

Sorry, to clarify, WEP or WPA would still allow your neighbors to sniff packets only difference is they're encrypted (not plain text). Basically, if someone really, really, really wants into your network...he will.

Mac authentication would prevent someone from connecting to your network but would not prevent him/her from sniffing packets. You'd need WEP or WPA for that, both are methods of encryption. Enable 128 bit WEP or WPA if all hardware supports it Turn on MAC authentication Disable SSID broadcasting There's tons of stuff written about this on the net. Google is your friend.

These are UNIX commands, no?

There's no way to do it "automatically" that I know of. The best way IMO is to hack shell32.dll or whatever icon library you're using. Re-checksum shell32.dll, compress it, and then add it to your unattended CD. Microangelo or Reshacker are some tools to use for editing libraries.

Ok, I got it to work. Here is the procedure for those that are interested. Bear in mind that this is for a very old laptop with little ram (40MB actually), a very small hard drive (1GB), and a non-bootable CD-Rom drive. Get the Win2K source and run nLite on it. Remove whatever you need except upgrade support (winnt.exe + setup.exe). nLite will also provide some warnings of things not to remove for laptops. Wipe everything from your target hard drive and destroy all existing partitions. Repartition the drive with one partition utilizing all available space. Format as FAT32. Copy the trimmed Win2K source to the target partition. I put my source (i386) in a folder named "source." For a laptop you'll need to get a USB adapter which allows a 44 pin HD to connect over USB or a 40 to 44 pin adapter to connect the drive to an IDE channel of your main machine. USB is more convenient as it is hot swappable. The research I've done shows that RIS installations will not work with PCMCIA ethernet adapters - maybe someone can prove me wrong. Create a bootable floppy. Make sure it has Fdisk, format, smartdrv, attrib, etc. on it (and other useful utils if you have room). Boot the machine with the floppy disk. Run smartdrv.exe (default params work fine). Then move to the i386 folder and execute "winnt." Now the first phase of setup will proceed. At the end you will be required to remove the boot floppy and restart. Here is where I encountered problems. If your machine does not restart and return to installer phase #2 (citing operating system not found or invalid partition table) you'll need to restart from the floppy and run Fdisk. It seems that winnt does not set the single partition on the HD as active so it is not seen at startup. Activate the partition in fdisk but don't mess with anything else. This will not harm any data on the disk. Remove the boot floppy and restart once again. If all goes well you should boot back to Windows installer. If it doesn't work, boot from the floppy again and check boot.ini in the root of your target hard drive. You may want to adjust the timeout value (-1 = no timer). My boot.ini file was trying to boot from the "old" operating system by default on a disactivated partition. No friggin' wonder it wouldn't boot up again! After modifying and saving boot.ini restart again and (cross fingers) you should get back to the installer. After this point I had no difficulties booting the machine or working in Windows 2000. My installation takes a little under 300MB (without paging file) if I remember correctly. So I have a whopping 700MB of PIO HD to play with! Good luck.

The CD is fine. I have successfully installed my nLite WIN2K in VMware. fake_url, I'm going to try your method (even though its really close to mine) this weekend.