gramaglia
-
Content count
90 -
Joined
-
Last visited
Never
Posts posted by gramaglia
-
-
Hi jdul, do u wanna piss everyone off now and again, again?
-
the correct manner to do it is to run
gpedit.msc
and then, from the
User Configuration
Administrative templates
System
Enable the "Disable Autoplay" policy
-
hey CM, what do u mean jdul is banned?!!!
The legend?????
naaaahhhhh, can't believe it!
How's happened?
-
Ok, guy, 2 or 3 serches and u're off....
Look, on Adaptec site they say u've got a integrated SCSI controller on your mainboard, so u'll have to watch at your mobo site, else they say that the file aic78xx.sys is the driver for you (on Windows NT). It seems strange to me, although, because some time ago I got a mainboard with that chip installed and it was discovered and installed by Win2k in a normal installation.
To see this go to: http://www.adaptec.com/support/7800productsupport.html
then tell me what u think about it.
Another question....Are u installing 9x and 2k on the SAME partition?
If so, DON'T EVEN THINK ABOUT IT!
9x -> FAT16 or FAT32
2k -> NTFS
OK?
-
Yeah, inferno, I suppose u're right....
So what about buying a 300 Watt Power Supply, (instead of the common 250, AMD just needs it), and upgrading all bioses and drivers?
Just came out a patch for win2k and AMD processors....try it.
-
I'll put my experience. I had a sb32pnp, and bought a pci 128.
You'll have to find what drivers u need (there are currently 4 or 5 types of sound cards that are named PCI 128, depending on the number following the CT characters.....
and in the end, it wasn't compatible with my mobo, so i returned to sb32pnp.
AnyWay my model was a CT 4810, and after 2 days of research I found it uses the drivers of a ES 1371 (Ensoniq!!!), a firm that creative bought long ago.
go on with awe64, my opinion.
-
Use 98lite IV, formidable what u can pull off from the beast.....
Anyway, I have only one reason to use it instead of 2000:WarCraft 2
One reason to use it instead of 98: NTFS 98 (on 98 and SE works not, on ME it works)
-
turned back to SB32PnP, now works great....
-
OK, WDM is the type of driver, the new Windows Driver Model, equal for win9x and win2k (NT family).
I have the ES 1371 also, (on card there is the name CT 4810), so what about downloading the newest drivers from:
ftp://download.intel.com/design/motherbd/ea/4035FULL.exe
They are claimed to be compatible with Win98/ME/2k. (WDM Family)
I tried them winth WinME and they run ok!
They are designed for Win2k, so I think you'll be well with them.
-
Just done, bobbin.
Solved nothing.
It seems though to be a problem with Advanced Power Management, or what WinME uses to manage Standby and so on....
I'll try to delete the driver from the components tree and see what happens.
-
Just another thing....
Nero, to be used under Win2k, must have Administrator Privileges. That mean that to use Nero, u must login as an Admin.
Don't know why. I asked Ahead, but after 4 months I lost hope to have an answer.....
-
OK, Nero doesn't use ASPI under Win2k, I know because I have Nero Installed under Win2k, and no ASPI driver Installed.
I knew the controller needed drivers, It wasn't on the HCL when Win2k was released.
I have the same CD Recorder, and a DC 310.
Fully supported, no problems.
Did u try getting new drivers from Tekram site?
If u have Adaptec EZCD Creator installed, remove it. If Nero is present, U won't need it. Instead, use WinONCD if u must....
-
Well, it's WinME... Installing Win98SE DOES resolve the problem....But not the IRQ Steering.
Anyway, no more blue screens
-
Yes, if you won't use a ES1371 as Sound Card
(SB AudioPCI 128)
-
-
Hi Jdul, How are u? OK, SB 128, but what SB 128?
CT48xx?
ES137X?
there are many models, please tell me which model.
Moreover, a week ago in the main page of NTcompatible appeared the link to New Drivers for PCI 128.
Give 'em a try.
-
SFC is still here, but u can call it only from the windows help center.
Start -> Help -> Tools
-
Ok, the four options are
1)Get IRQ Table using ACPI Bios
2)Get IRQ Table using MS specification Table
3)Get IRQ Table from Protected Mode PCIBIOS 2.1 call
4)Get IRQ Table from Real Mode PCIBIOS 2.1 call
The 4th option has always been greyed out.
The error was given with option 1 and 2 enabled.
When I disabled the first and enabled the 3rd, there were no more problems, but blue screens continue, (much more rarely, but they come).
Does anyone know the right option to enable?
It's a Pentium MMX 233, with a VX chipset, 64MB RAM, one SCSI PCI controller and a SCSI ISA controller, a Voodoo Banshee PCI, and the AudioPCI 128 (CT4810) Sound Card.
CT4810 and ES1371 are the same card.
-
Ok Jdul thanks.I tried Creative drivers and things are somewhat better, but the error, although less frequently, comes back again. I tried also the newest downloaded from Intel (WDM drivers), but to no avail...
Then I noticed another strange thing, WinME tells that the IRQ Steering has some problems getting the peripherals listing, but there is not a warning sign at all, I looked just to be sure....
Should I change the way Windows interrogates the Bus? There are 3 choices (4, but one is greyed out)
- Microsoft
- BIOS
- Another way I just can't remember, I'll look when I return home tonight...
More to come! (If u are interested )
-
thanks, mister Eddie... Other ideas from anyone?
-
Currently, I know there is a detailed procedure on the Windows NT Resource kit that tells exactly how to resolve your problem, but I have no more this book, that was lent to me by a friend and I can't remember it. Guys out there, is there anyone that has the Reskit books?
I'll search for it meanwhile, ok?
-
Why not posting instead Binary Dumps of the code? Pretending to understand it!!!
Ehm, jdul..... look who's talking, ah?
-
If so, why not replying to my problem (possibly with something that will permit me to solve it?).
Many thanks in advance
-
Eddie, didn't know what to do at 23:52 of 15 sept?
Conexant/Brooks 56K AC-Link Modem Problems
in Hardware
Posted
I too have a conexant modem, HSF drivers required, but no driver seems to work. So I bought a 3com 56k. Other way to resolve the problem is to wait the correct driver from Conexant. Sorry, but I wasn't able to help myself too.......