Cynan

Nope. Seems fine to me.

Is it just me or is Obiwan's voice/dialogue kinda annoying ?

Use VMware or Virtual PC.

Faulty MB? PSU? Memory?

Actually you can change the HAL in Device Manager but its not recommended.

Depends on your definition of a virus really ! Some quite useful programs could be classed as them.

*sigh* Now I'm not gonna pretend I know what I'm doing here, because truth be known I don't. I've heard a lot about various different SCSI configs. and how they are set up, but I've always been a lil hazy on the whole thing. So I'll just describe what I have, what I've tried, and whats going on... hopefully someone can help me I have an Adpatec AHA-2940AU SCSI card connected to a Yamaha CRW4260 CDRW drive. Termination on the card is set to automatic, a parity jumper is set on the drive and the termination jumper is off. Now with this setup I've been able to use the drive for reading and writing in Windows 9x/ME and NT/2K with no problems. Now that I come to use Windows XP, I suddenly get Event 11 error messages in the event viewer ("The driver detected a controller error on \Device\Scsi\aic78xx1"). The weird thing is that Nero would let me burn VCDs no problem, but not data CDs. So after messing around with setting the termination to enabled on the card and placing a jumper on the drive and getting no where. I decided to reinstall XP and give a flesh install ago (I previously did an upgrade from 2K). This time I couldn't burn at all. Tried with termination on and off again, but nothing. So I installed the ASPI layer and I got back to where I was in the first place. I can burn VCDs, but no data CDs, but this time with a difference. If I have termination off, I don't get the Event 11 error anymore but instead I get an occasional Event 51 ("An error was detected on device \Device\CdRom2 during a paging operation"). With it enabled, I get Event 11 again. Still though, I can only burn VCDs... whats with that? surely I should be able to burn a CD or not. At this point in time I'm seriously thinking of scrapping any future thoughts of going total SCSI and just stick with IDE - least it works ! (well never failed me anyway). Oh I also updated the fireware on my drive too, just to check if that fixed it. No dice. So. At this point I'm gonna follow up any leads, no matter how trival! I don't want to buy a new drive, but I'm seriously considering it (an IDE one at that!). Thanks for any help (I need it), --Cynan.

ITS FIXED! YES! I saw the new Adaptec ASPI drivers and installed those, removed the older 2K ones that the README says were no longer required, and now it all works! WOO F'IN HOO ! (Excuse me there, just a bit happy!).

I know this is old news now, but I found this from a previous topic about this in my saves messages, so I thought I'd post it.. Quote: The official word from MS at one time was that it stood for "New Technology". Which was pretty funny, since it has very strong roots in the internals of DEC's VMS, the keel for which was laid in 1976 or so... pre[censored] Windows (non-NT, non-9x) and even MS-DOS by quite a few years, and still (many major releases that did NOT involve name changes, only "honest" version numbers, later) easily the most reliable general-purpose, production-grade OS available. (It's not difficult to keep a VMScluster up for YEARS, sailing right through complete replacement/upgrades of all hardware, OS upgrades through both minor and major revs, etc., and maintain service to clients the whole time. Tandem's "NonStop" OS, long since also absorbed by Compaq, can do the same, but I don't consider it "general purpose"; it is too focused on transaction processing and database access.) It was fun to go around pointing out that if you take "VMS" and advance each letter by one place in the alphabet, VMS => WNT. i.e. WNT = VMS + 1. David Cutler swore this was accidental and that if they'd noticed it early enough they'd have changed it. David Cutler also was one of the principal designers and coders for THREE other OS's at DEC, RSX-11M, (then VMS), ELN, and Mica - the last one never shipped, which is why he was annoyed and available for hiring by MS to build their new OS. Full story on this is in an interesting little book called Showstopper. And yes, Mica looked sort of halfway between VMS and NT in its design. Considering that most of us never get to design even one OS from scratch, the man is definitely over his quota... Why wasn't Win2K called Windows NT Version 5? Well, fact is that a company called Northern Telecom (now Nortel Communictaions) owned the trademark "NT" for use on computer and communications equipment (it's even their stock symbol). They licensed it to MS for a while. Might have gotten fairly confusing, too, since it seems they were using NT4 as the core for some of their phone products, so you had an NT (Northern Telecom) switch running NT (the operating system)... Anyway, one story is that they eventually decided to either not renew the name license to MS at all or to charge too much, so MS said "fine, we'll call our OS something else." Another is that "it was a marketing decision". I'm not sure whom to believe.

I have similar problems.. though its related to my SCSI controller, but still, disc-at-once is better imo.

Unknown Flash Type... maybe its not the BIOS bin file, or the software, but perhaps the BIOS chip in the machine is non-standard... just a thought.

If you have an EPROM programmer handy, or know someone with one, I'd use that. I don't know why its failing on your machine though. Are you sure its the right BIOS ?

Aaaahh SUPER Drive! Gotcha ! heh. I was thinking you just meant a floppy... sorry no experience with that !

Either there will be a setting in your BIOS on about it, or you have connected drive Bs connector to the drive, try using the last connector on the cable - floppys still use cable select see to determine which is A and B (afaik).

I've never been a fan of Diskeeper.. perhaps I'll take your word on version 7 though and take a look at it at some point. As for SpeedDisk, I'm using that happily. The first version for NT that came out was a bit dodgy, but it seems okay now, and in my opinion, a lot better them most of the others out there.

I thought you were a fan DosFreak... ? ?

Read the manual dude.

You want to get into DOS. You can use any DOS disk thats bootable. NT doesn't have DOS, i.e. no such thing as an "NT Boot Disk". If the disk isn't booting then you should check in your BIOS and make sure that the boot sequence checks the floppy before your hard disk.

If you go to BootDisk, download the bootdisk maker for Windows 98 and then run it. This will create the bootdisk for you. You can then copy the NTFSDOS files onto that disk too, and when you have booted up on that disk, run NTFSDOS. This will give you access to your NTFS drives.

www.bootdisk.com has all the boot up stuff you need. Make a Win98 boot disk, then copy the NTFSDOS stuff across, and vala!

Get a super soaker and soke them out the window

winipconfig ? It comes with the Win 9x line - 98 (and up I presume).

Go to SysInternals and download NTFSDOS. Stick that on a normal floppy and when you've booted up, you run that, and then you will be able to see your NT drives and copy files from it. If you pay for the full version, then you will be able to write to the drive too. Alternatively, you could get the linux version which is free.

It is the hardware and the drivers. Driver wise they aren't thread safe, hardware wise they draw the full 500ma and sometimes, it trys to draw a bot more.. thats what MB USB ports can't hack.

Hey all, I'm in current need of a SCSI CD-ROM drive and the only one I have is currently in my main machine, which I don't want to switch off and have any downtime. So. My question is, can I just pull out the ribbon cable and connect it up to another system? SCSI can do that right? and if so, are they're any requirements (you know, disabling things etc) that I need to do before I do it? I'm running WinXP atm for reference btw. Thanks. --Cynan.