I have been trying to reinstall win2k for 3 months now, and a friend referred me here (said it was great service). I am using a millenia max xp dream machine (actually meant for windows me), and have been running windows xp and windows 2000 on it before. I am using Promise fasttrak(tm) 100 controllers, and when I try to put the floppy with the drivers on it after F6 on the win2k setup and select the correct driver, I get the error "FASTRAK.SYS has caused an unexpected error(18) at line 1211 in D:\nt\private\ntos\boot\setup\oemdisk.c." If anyone has an answer to this problem it would be greatly appreciated.

Three months? You're tenacious; I'll give you that. :) Looks to me like your CD may be bad.

Life is more painless for those who are brainless.

Unless a cd is seriously scratched I can't see how it would fail if previously running OK...?

I'd be inclined to look a little at RAM...; reduce to a single stick (min 128Meg) and see how it goes? Likewise the drive is actually (still) OK; scan/checkdisk routine?

Possibly too, even though you say you had XP/W2K previously on this PC (originally spec'd for ME)..., I'd be inclined to vet this system for W2K compliance via the WS2K readiness analyzer); and also to visit the web-site for the system - to see if there are any drivers etc. you may need to supply...

Presumably this system is being (re)formatted during W2Ksetup; and not preformatted via (an) ME bootdisk...? If you were to use an ME bootdisk to preformat as fat32, then W2K would not be at all happy with that fat32 area; W2K doesn't like the ME versions... and won't install there...

One other thought, with Jennifer's observation in mind... can you secure a fresh set of drivers - either off the web-site for Promise, or a replacement CD; as this would then rule out the CD either way?

Maybe I am wrong but it seems that Windows is looking at a driver off the CD instead of the one provided by the floppy.

As OtheHill might be able to tell you, I know for a fact those Promise cards can give you a fit!
Have you tried to install WIndows without the drivers, then try to install them after you're up and running?

I love Humanity - It's the people I can't stand

The first problem that everyone suggests is that the cd is bad, but I checked that and it's fine. I even tried to reinstall from the UI of win ME, and the problem was with the drivers. I also installed other drivers, but the Promise drivers are the only ones that cause problems. If anyone has already installed with Promise Fasttrak drivers, please tell me how you structured the drivers floppy. I am using the Promise Fasttrak 100 Ultra ATA/100 Raid card, but the Ultra100 drivers are incompatible with the card according to windows ME. So I installed the Win2000 Promise Fasttrak(tm) 100 controllers, which worked fine until the install. I remember having to fight with the install the first time I installed the system, but I don't remember what I did. I found a Hard Drive Diagnostics and Utilities floppy, but I don't know how to use it. Any suggestions?
I ran scandisk and it said the disk drive was fine. If anyone could tell me the compatibility website for win2k that would be great, because the one on the CD is down. This system is indeed being reformated by the win2k cd, but I never got past the menu.
Because, as RagingBhuddist suggested, I have tried to install win2k without the drivers, but when I get to the menu and hit enter to install windows, I get the message "Setup did not find any hard disk drives installed on your computer...this may involve running a ... setup or diagnostics disk," which is where the idea for the hard drive floppy came in. OtheHill, I understand that you have experience with driver installation, and I didn't fully understand how to solve the possible problem described in your message, so more help would be greatly appreciated. By the way, the drivers are brand new (reinstalled them yesterday again).
Sorry for such a long post, but I think that the prior informaiton and the following is neccessary. When I try to reinstall win2k from the UI of Windows ME, the whole proccess goes fine until I have to restart my computer, which goes fine as well. The problem is when the win2k setup tries to load the menu (I haven't setup any drivers in the UI version), I get the "inaccessible_boot_device" error. Thank's for all the responses, and any future ones.

You give too much credit. I have had my share of issues installing Win2000. My take on 2000 is that due to the fact it was never intended as a general OS there is a scarcity of drivers on the disk. My response #3 may not be correct but what I meant be it was that Windows may not be accessing the drivers on the floppy and instead looking on the CD. Not finding suitable drivers on the CD then generates an error. If the drivers for the controller card are like most driver packages there are drivers for multiple OSes. Maybe placing only the appropriate driver on the disk would help. Slipstreaming the driver into a Win2000sp4 CD would probably be even better. I am not capable of advising you on HOW to accomplish that though. I am pretty sure there are folks here that could help with it. On that same subject, trvlr mentioned in response #2 that your hardware may not be ready for Win2000. I don't know if the compliance analyzer is still available but it would point to the hardware that is problematic. You could then collect appropriate drivers for all the problem hardware and supply them all at once. You may not have any other issues beside the obvious controller card. It appears that Win2000 has issues with controller cards so I suggest you look at:
http://www.promise.com/support/faq/faq_eng.asp

As I indicated in my earlier post... W2K will not at all be happy with a fat32 location in anyway formatted by ME; at the least W2K wants a fat32 system partition for the boot/start-up files that has either beenformatted via W2K,or via a '98 bootdisk (format util; it may (often will) then install to another partition (its actual boot-partition if its system files are not going into the system partition) OK.

But as you're starting afresh and reformatting the drive anew, that issue wouldn't apply here?

It does sound like a driver issue but who knows...; MoBo drivers various, chipset etc. may also be part of the problem. Have you checked with the web-site for MoBo etc.?

I'm suspicious about the system being OK for W2K - as you say it was an ME based sysem initially...

The readiness analyzer is (was) on some W2K CDs'; had become to hard to find in M$-land (why...?); but looks like it's there again...

http://www.microsoft.com/downloads/details.aspx?FamilyID=B008D64C-DD8D-4816-A3D9-FD2ED787E735&displaylang=en

is the actual (long......) link; or go to the downloads section and search for windows 2000 readiness analyzer. You ought then to get to the same place?

This is what the analyzer said about my computer, and it seems that all it says is that I need the drivers floppy which it isn't reading, but I'm no expert, so if someone has different ideas it would be really helpful. Here's the report:

Incompatible Hardware

The following hardware may not support Windows 2000 without
additional files. Please see the Microsoft Windows 2000 Hardware
Compatibility List at
http://www.microsoft.com/windows2000/compatible/ for a list of
compatible hardware. (Some of the following entries might be software
that is registered as hardware.)

Display adapters
NVIDIA GeForce2 Ultra (Micron)

Network Service
File and printer sharing for Microsoft Networks

SCSI controllers
Win2000 Promise FastTrak100 (tm) Controller

Sound, video and game controllers
BDA IPSink (not currently present)
BDA MPE Filter (not currently present)
BDA Slip De-Framer (not currently present)
Microsoft Kernel Audio Splitter (not currently present)
Microsoft Kernel DRM Descrambler Filter (not currently present)
NABTS/FEC VBI Codec (not currently present)
VIA AC'97 Audio Controller (WDM)
World Standard Teletext Codec (not currently present)

WDM Modem Enumerator
MSP5900-U WDM Driver

You can continue with the upgrade, but the hardware may not work
until you supply the additional files.

Software Incompatible with Windows 2000
----------
This section lists information about programs that are incompatible
with Windows 2000. Before upgrading, evaluate how important these
programs are to you.

Software That Does Not Support Windows 2000

Setup has found programs on your computer that do not support Windows
2000. Contact your software vendors to obtain updates or Windows
2000-compatible versions. If you don’t update these programs before
you upgrade, the programs will not work.

Disc Detector (in Control Panel)
MSP5900-U WDM Driver (in Control Panel)
VIA V-Raid Utility (on the Start menu)
Windows Movie Maker (on the Start menu)

Before you upgrade to Windows 2000, you should remove any
incompatible programs. After the upgrade, uninstall might not work.
Add/Remove Programs in Control Panel can help you uninstall most
programs. Click Start, point to Settings, click Control Panel, and
then click Add/Remove Programs.

Incompatible Hardware Accessories

The following programs support your computer hardware; however, they
are incompatible with Windows 2000. To see whether updated versions
of these programs are available, visit your hardware manufacturer's
Web site.

Creative Labs SoundBlaster Accessories

General Information
-------------------
This section provides important information that you need to be aware
of before you upgrade.

Backup Files Found

Setup found files on your computer that appear to be a backup of
part of Microsoft Windows ME. During the upgrade to Windows 2000,
Setup removes Microsoft Windows ME from your computer, including
any backups you may have on your hard disk. More information is
available in the Setupact.log file, located in your Windows
folder. It lists 12 folders that might contain backup files.

Protect your backup files by copying them to floppy disks, a
network server, a compressed archive file, or other backup
mechanism.

Recycle Bin

Setup found 1 files in your Recycle Bin. If you continue
upgrading to Windows 2000, these files will be deleted.

Upgrade Pack Information
------------------------
The following information was provided by upgrade packs.

Microsoft DirectX 9.0

To maintain compatibility with your DirectX 9.0 applications, you
will need to download the DirectX 9.0 update for Windows 2000
from http://windowsupdate.microsoft.com.

I'm sorry trvlr, but I don't really understand what you said about formatting the disk drives with windows ME not working with win2k, but I am now running windows ME, so how would I fix the fat32 problem (maybe it isn't a problem, I remember I had fat32 formatted drives in xp)?

Othehill, I can't find the faq for my ultra 100 driver. Probably something stupid on my part. sorry.

That site asks for card model numbers. You need that number. I am a lillle confused now. I thought you were attempting to perform a fresh install of Win2000 but it appears you currently have WinME installed. trvlr means that your current installation was performed using the WinME FAT32 format process. If possible it would be best if you could save any files currently on your computer and start over with a fresh install of Win2000. If you decide to do that you should collect any and all necessary drivers prior to wiping the drive.
If you instist on attempting an upgrade you need to get drivers for most of the hardware in your computer. All the devices listed. What service pack is included in the Win2000CD that you have? Service pack one doesn't support DX9, which you currently have. This means you could have issues with the graphics card when installing. The way around that is to back out of the installation of the card and instead let Windows install a generic VGA card. You can updaate the graphics driver after applying sp4.
This is why most folks just buy a new computer.
Addendum, I hope you understood the compatibility report. You even have software that isn't compatible with Win2000. You might be better served, if you NEED that software to stick with WindowsME.

W2K has an issue with a fat32 location formatted by ME - be it via an ME boot-disk util, ME set-up, or a working ME installation. W2K will apparently install its system files (the actual OS itself) to an ME fat32 formatted (non-Primary) location (i.e. an extended partition/logical-drive) – BUT the W2K boot/start-up files will NOT install etc. to an ME formatted system partition – i.e. the active Primary… Thus you could have a ’98 formatted system (active Primary) partition and an ME formatted system partitions; and it probably would work… It has for some folks apparently.

It’s all to do with the genealogy of W2K and ME… ME arrived at W2K and W2K doesn’t know/recognise its cousin – or its progeny etc… This issue does not exist with XP and ME…

In your sistuation… you effectively have to remove ME and reformat that Primary – either with a ‘98SE boot-disk util, or allow W2K set-up to do it for you…; or create a second/additional Primary and install W2K there… To this end you could use an add-in boot-util – BootITNG is one that gets good reports… I haven’t used it so can’t advise further on how to go about it with that util. I caution against using PM; XP + PM has meant problems for some (not all) folks, and you have problems enough already.

Also, can you obtain/transfer the Promise drivers to a floppy and (presuming this system has a working floppy-drive) provide them that way? I doubt it will resolve your current dilemma however – for the ME/fat32 issue detailed above; but it may not hurt to try – who knows?

"OtheHill" has covered the essential/critcal details from the W2K readiness util; and your main W2K/ME issue (ME/fat32) is not mentioned by that util...; which is hardly surprsing as ME wasn't around when W2K arrived etc...

I'm reasonably certain that your problem is primarily the ME formatted fat32 Primary; W2K just does't like it!

victor-
I'm confused too. Do you have 2000 running or ME? Or did you try to install 2000 over an ME install? Or...?

trvlr -
I'm not sure why you would say W2K won't install to a FAT32 drive or partition that was ME formatted. I've been running 2000 for about 8 years now and always used an ME boot disk and an ME install CD to format the drive. And it seems it wasn't until I "upgraded" to NTFS that I suddenly find myself all over this forum, trying to repair problems...

I love Humanity - It's the people I can't stand

This ME/fat32 was an issue flagged up, in the early days of W2K, by John Savill in his NT-faqs on what was then NT later Windows2000Mag; and also within the magazine itself I think...? (and I think there is reference too about it in M$-land...) Certainly there is no upgrade path from ME to W2K - and this is clearly stated by M$...

There have been quite a few instances where this was an issue for folks various; and reformatting as fat32 via '98SE boot-disk util or during W2K set-up provided the resolution; and equally (as usual...) many didn't have the problem.

As I indicated earlier it seemed to be mainly affecting the system partition (where the boot/start-up files reside). W2K does not apparently (for many installations) like an ME formatted fat32 system partition. If this was a combined system/boot-partition installation (i.e. both system and boot files in the active Primary) then again the problem occurred for many (but apparently not all) folks. Similarly for an intallation with the two partitions are/were separate the problem was frequently encountered... but apparently not always...

It did not occur (as far as I can ascertain) if the system partition was (pre)formatted via '98 - be it a situation were the system partition was separate from the boot-partition, or with an all-in one installation (system/boot-paritions in the active Primary. And this has certainly been my own experience re' 98... Studiously avoided ME for many reasons...

Sorry for the confusion; when the install didn't work without a ui, I decided that if I install a lower os (such as ME), I could upgrade from its ui. Obviously that was a bad idea. The end result is supposed to be installing windows xp on my system. So if I uninstall windows me and run the win2k setup form the cd, it should work? Won't the drives still be formatted to fat32 during the cd setup? How could I preformat to win 98 without 98 cd? Sorry, I am really bad with os' (especially windows).
trvlr-
I always had the drivers on a floppy. Sorry for the confusion.

"...The end result is supposed to be installing XP..." Thus no need to involve W2K at all; simply pop in XP CD and away you go... (allow it to reformat the target partition during setup...)?

'98 Fdisk/Format utils are on the '98 bootdisk (usually), although there are versions of the boot-disk that do not ahve an expanded format util; it's there in the compressed/cab files - and has to expanded to the floppy in order for you to use it...

If you don't have one download an image from bootdisk.com - get the '98SE version with the (expanded) format util included + CDROM drivers; save to a hard-drive - expand to a floppy, and use that floppy.

Still if you were using either W2K or XP CD, then yes during setup you have the option to reformat the targeted area accordingly (be it fat32 or ntfs...).

Thus you can install W2K - all things being equal without involving ME (as long as the W2K CD is a full version)

But again you seem to want XP - so why bother going thru' the trials/tribulations of installing W2K; just go straight ahead with XP?

If your XP CD is Upgrade then you need a compliant OS (CD usually these days) to satisfy proof of a qualifying OS for an Upgrade CD to install - be it as an Upgrade of an existing OS or as clean/fresh start...

Just to clarify trvlr's last statement. If you are using an upgrade WinXP CD then when windows asks for proof of a authorized upgrade OS simply pop in the Win2000 CD and you should be good to go.
Why in the world didn't you think to tell us that the ultimate goal was XP?

And if your W2K CD is also an Upgrade CD then pop in the ME CD providing it's a Full version CD. If that ME CD is also an Upgrade then you have a problem...

The issue with windows xp is that when I try to install the drivers, it gives me the error I mentioned above; "FASTRAK.SYS has caused an unexpected error(18) at line 1211 in D:\nt\private\ntos\boot\setup\oemdisk.c," which is why I decided that maybe it would work as an upgrade from win2k.

You "seem" to be saying that W2K will go in OK? Presuming so, then there is an issue with the XP drivers for the Promise card... Possibly this card is no good for XP?

If there is an issue with the card and XP, perhaps contact Promise for their advice/help - if any forthcoming?

No, win2k gives the same error.

mmm - I know it's a long shot... but think about RAM... Can you reduce to a single stick (min 128Meg) and have a go again; perhpas try each stick in turn - oresuming two or more present. Even better beg/borrow/st..l a "known to be good" stick and try that too?

Why I suggest RAM may an issue here is that setup appears to get stuck at the same spot each time; and during setup RAM is involved... Possibly (and I do empahsise - possibly - as this is not exactly scientific in terms of an explanation... ) setup is trying to address an area of RAM that is less than it might be and the error you get reflects the data attempting to write to that area...? The resultant misdirect implies a problem with the source disk/file and it ain't?

Are you sure the drivers you are attempting to use were written for 2000/XP?

He does seem pretty firm on that they are... but who knows...?

Sniffing around the Promise site has me thinking this card is not exactly new...; possibly they have replaced it with another (better) one as well; and one that did work better (properly???) with W2K/XP?

(Ffrom a few comments I've seen here and elsewhere...) Promise have appear to have produced a few problem cards from time to time...? Perhaps this is one of those?

Drivers for one in question are at:

http://www.promise.com/support/download/download2_eng.asp?productId=15&category=driver&os=0&go=GO

and one can see they are "quite olde..." by their published dates...

I just looked in my bois to see how things were going there, and now my hard drive isn't being detected! How do I fix that?
Also, the reason I went in was to check my boot sequence; cd, floppy, ide-0. Is that right for an install?
Sorry for such a long posting, and thank you for all the help. I know I haven't been easy to deal with.

By the way, the drivers were definetly designed for win2k/xp. Please remember that I had win2k and xp running on this computer.