Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: wily who wrote (10596)	3/5/2000 1:18:00 PM
From: Dan Spangenberg	Respond to of 14778

FWIW, I have Win2000 OEM running on both a BH6 and a BP6. I've done quite a few Win2000 installs now without really any troubles. A couple things I have found from my own experience, not sure if they are documented issues. On my NT and 2000 boxes, I always use NTFS and so I prefer to put a DOS bootable partition (formatted FAT16) on the drive first as C: and then the NTFS system partition for NT or 2000 second. I have had trouble getting 2000 to get all the way through an install when that first FAT partition is a full 2 gig in size. I sized it down to 1 gig or smaller and then Win2000 installs fine. I have had this happen three times now, but haven't searched anything to see what the exact issue is. I have also heard of some troubles installing 2000 on a very large drive, unpartitioned. I usually always stay around the 4 gig range for the system partition and the remainder of the drive as a large data partition. so I haven't personally experienced this problem. All in all I love Win2000. I had to do an NT install the other day, and sure missed all the niceities of 2000, in fact, it was quite a pain to install and setup in comparision. :-) Not sure if this info will help you. Good Luck Dan

To: wily who wrote (10596)	3/5/2000 5:16:00 PM
From: jw	Read Replies (1) \| Respond to of 14778

Dan & Howard covered the subject Very Nice. Some more reading in spare time. I'm almost too irritated to talk about it yet (it's been about a week since I gave up trying). No, No, too early to give up. PS I know you're going to ask did I do the BIOS update to NV something or other: yes, (cool thingie!)., You don't want to hear my story about Bios Flash, scary. 3 hrs. in Tech shop, $160 later, it works. Could have bought The NV Bios from Abit for $10. Later, <G>, /jw ----------- This week our tech tips will cover Windows 2000 in general and some installation tips we have learned since the release. For those of you that haven't used W2K in any of the pre-release forms, when you install the OS you will find that it is very simple to work with if you have some previous NT experience. You will have the option of either installing the OS from a Win98 desktop or you can boot to the CD to do the installation directly on start up. If a dual boot system with Win98 is preferable, then there are a couple of suggestions we have found useful. I find that when installing the dual Win98 and W2K OS, it is practical to make a separate partition for each OS. You can easily do this from FDISK with a WIN98 boot disk, making the partitions what ever size you prefer. You can then install your Win98 OS - install all drivers and software then reboot to the Win2K CD for installation again. When installing 2000, and if using a storage device, such as the HighPoint ATA66 controller or Adaptec 2940U2W, hit F6 on the first screen of the setup. This will allow you to install the drivers for mass storage devices. Any other non-native storage controllers should be installed at the same time. You will also have the option of installing 2000 on NTFS or FAT32. Since you made another partition already, you can then continue installing the OS with FAT32 or convert it to NTFS. Remember, Win98 doesn't read NTFS, so if sharing data between the two OS's is what you want, better make it Fat 32. The question of why make two separate partitions is in the air. If you don't make a separate partition, then when installing 2000, any driver of Internet Explorer or Outlook files will be over written in the C;\Program Files folder. The only way to prevent this is to separate the OS. You could also install the OS's in the same partition then make a separate Program Files_2000 folder, but you aren't going to remember to change the default folder every time you install something. So if it was installed in 98 and you installed it in 2000, then chances are that it isn't going to be right in 98. If you are installing 2000 as a single operating system, just boot to the CDROM to start the installation. You will have to make sure the the boot sequence is correct in the BIOS: CDROM C A would work fine. Most of the add-on cards you will be installing will have native drivers within 2000. There are a few exceptions and you will have to be prepared to go the the manufacturers web site to download the 2000 drivers...if available. The Matrox G-400 video card will be one for sure. If using the Abit BP-6 or Abit BE-6 boards, you will have to download the 2000 ATA66 drivers from Highpoint. For most AGP video cards, be sure that the AGP slot has an IRQ Assigned enabled or 2000 probably won't be able to load the drivers correctly. USB is usable in 2000 also, so you may as well have that enabled also if you plan on using USB devices. From our experience with 2000 since the Beta program started, we find that the 2000 PNP appears to be the same as Win98. We loaded a PC with 4 PCI cards and 1 Agp card this week and 2000 found a home for all of them just like Win98. Not something that is likely under NT4, which requires a separate IRQ for every device. When loading a PNP OS to the max with add-on cards, you may have to manipulate the cards to find a sharing partner with them all. Some cards require a separate IRQ and will not share. Most SCSI cards like to be by themselves. PCI Modems will share as well as NIC cards. You will have to probably fine the right partner for the SB Live card, but it can be done. So while 2000 may seem a bit overwhelming to some, it really is a lot easier that NT4 to install. Once the driver shortage is overcome in the next few months, I think we will find that it will or may be the OS of choice. Remember, 2000 is multi-threaded and will take advantage of dual processors. ========================================= If installing 2000 as a clean install, (no other OS on the drive and un-formatted) you need to set the Boot Sequence to: CDROM - A- C in the BIOS. Then start the machine and it will say on the 4th screen: "Press any key to boot to CDROM" - Do that then on the first blue screen press F6 to install the ATA66 drivers from highpoint if using an ATA66 drive or SCSI Controller. If using an ATA66 Drive, we will assume you have already downloaded the 2000 Highpoint drivers from either Highpoint or bp6.com. If using a Ultra 33 disk. just continue the installation without any 3rd party drivers. BTW, you have to have a CD installed in the system to install 2000. ------------------------------------------------------------ <BH6 IRQ resources> AGP and PCI-1 share an IRQ PCI-2 owns independent IRQ PCI-3 owns independent IRQ PCI-4, PCI-5 and USB share an IRQ Manually assign IRQ is possible in BIOS "PnP/PCI configuration" page, PIRQ_0 is for AGP and PCI-1 PIRQ_1 is for PCI-2 PIRQ_2 is for PCI-3 PIRQ_3 is for PCI-4, PCI-5 and USB Please try manually assigning IRQs for PCI slots to avoid conflict with ISA SCSI or any other resources.