Xp 2485
I see that 2485 is out (or at least leaked to the 'net). . . . Anyone running it yet? If so, how's everything look in comparison to 2481?.
I see that 2485 is out (or at least leaked to the 'net).... Anyone running it yet? If so, how's everything look in comparison to 2481?
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Cool. Good to know that it's faster. 2465 was OK once it was running, but when I logged in to my domain, it took a little while for the Start Menu to be usable. 2481 fixed that, but I'm always on the look out for more speed! 
If everything goes as planned, the next release should be RC1 - probably build 249x. It's supposed to be out within the next 10 days, but could be delayed a little bit.
If everything goes as planned, the next release should be RC1 - probably build 249x. It's supposed to be out within the next 10 days, but could be delayed a little bit.
Works good here,
apparently the 2474 reset fixes don't work, but I'm sure i'll find out soon enough.
Did notice a few things, the sound crackling on my philips acoustic edge is still there even with the new philips drivers.
My sblive on my work box is ok but the main volume doens't do anything anymore(gonna do the windows update and if that doesn't work then to the 3209 version of the 5.1 drivers)
Aside from that a massive build # increase in dx and works good with the nv 12.60 drivers(I used the 620 interim release on 2481 and the 12.60's problems I had went away.
btw use the NvQtwk.dll from 11.01 or any release around there to get your overclocking to stick in 2k/xp on boot.
apparently the 2474 reset fixes don't work, but I'm sure i'll find out soon enough.
Did notice a few things, the sound crackling on my philips acoustic edge is still there even with the new philips drivers.
My sblive on my work box is ok but the main volume doens't do anything anymore(gonna do the windows update and if that doesn't work then to the 3209 version of the 5.1 drivers)
Aside from that a massive build # increase in dx and works good with the nv 12.60 drivers(I used the 620 interim release on 2481 and the 12.60's problems I had went away.
btw use the NvQtwk.dll from 11.01 or any release around there to get your overclocking to stick in 2k/xp on boot.
No, the 247x-2481 cracks don't work on 2485, much like the 246x cracks didn't with 2475 or 2481. Microsoft's engineers are working at a frantic pace to try to keep ahead of the crackers, but usually there's a crack available within hours of a build's release... and, yes, there is one for 2485.
I'll still probably purchase the OS outright when it comes out, but I really don't like the activation thing.... I also hope they price it at a reasonable level.... The prices for Office XP UPGRADES are WAY too much.... More than half the full version's retail price....
I'll still probably purchase the OS outright when it comes out, but I really don't like the activation thing.... I also hope they price it at a reasonable level.... The prices for Office XP UPGRADES are WAY too much.... More than half the full version's retail price....
Well the sblive SBL512013209 drivers dont' work in 2485 but that could just be the install I'm working with(windows update sblive driver doens't install either)
the main system volume doesn't do anything still and the wave volume and winamp have to be almost at right at the point of being all the way down to get a tolerable volume level, otherwise it's way too damn loud.
A new crack would be good but if the crackers were smart they woudnt' crack it at all till it's finished and then crack it when its too late.
the main system volume doesn't do anything still and the wave volume and winamp have to be almost at right at the point of being all the way down to get a tolerable volume level, otherwise it's way too damn loud.
A new crack would be good but if the crackers were smart they woudnt' crack it at all till it's finished and then crack it when its too late.
My mouse is really sluggish under 2485...
MS Intellimouse Explorer. Don't know whether its the mouse itself or the graphics drivers?
Athlon 1.2Ghz
Abit KT7A RAID
640Mb RAM
Elsa Gladiac Geforce 3
SB Live
3Com 10/100 NIC
Homer
MS Intellimouse Explorer. Don't know whether its the mouse itself or the graphics drivers?
Athlon 1.2Ghz
Abit KT7A RAID
640Mb RAM
Elsa Gladiac Geforce 3
SB Live
3Com 10/100 NIC
Homer
2485 is working great here. No driver issues at all. Wish they would slow down with releases hehehe, seems like all I do anymore is run a new beta build through my own unscientific torture test.
Its strange with the mouse thing, as I hadn't had that since early Beta 1.
I'm not completely sure it is the mouse causing the problem. The redraw on certain objects is terrible, using the Windows XP themes.
Info Tooltips and bubbles have massive black squares behind them when they appear, but redraw to remove it....
Most confusing.
Also I get bad popping with my SB Live (First build to have done that!)
Homer
I'm not completely sure it is the mouse causing the problem. The redraw on certain objects is terrible, using the Windows XP themes.
Info Tooltips and bubbles have massive black squares behind them when they appear, but redraw to remove it....
Most confusing.
Also I get bad popping with my SB Live (First build to have done that!)
Homer
Well, I deleted my install of 2485.
I read elsewhere in the forum that the mouse sluggishness might be related to ACPI.sys
But that thread came to the conclusion it was simply related to Multiprocessor Boards and ACPI.
I only have one processor on a KT7a RAID.
Having built and maintain computers for a number of years, I'm somewhat at a loss to understand why this sort of slowdown would be occuring.
Win2k operates fine.
Very Confused Homer
I read elsewhere in the forum that the mouse sluggishness might be related to ACPI.sys
But that thread came to the conclusion it was simply related to Multiprocessor Boards and ACPI.
I only have one processor on a KT7a RAID.
Having built and maintain computers for a number of years, I'm somewhat at a loss to understand why this sort of slowdown would be occuring.
Win2k operates fine.
Very Confused Homer
Microsoft has problems coding for their own stuff sometimes.... In 2465, I couldn't get my Microsoft Internet Pro keyboard to work right (the volume and mute buttons didn't function - they popped up on screen, but I couldn't change the settings).... I use a Logitech opitcal mouse and it works fine for all versions of Windows. A little trick I've been doing for stuff that worked in previous builds but not on the current one is taking the DLLs from the one it worked on and plugging them into the new OS... Usually works.
Remember, though.... 2485 is an internal build, so it's bound to cause problems for some people.... With internal builds, I've noticed that it either works great or not at all. I've had no problems with 2485 here (other than the to-be-expected things), even my Sound Blaster Live works fine....
Adrian
Remember, though.... 2485 is an internal build, so it's bound to cause problems for some people.... With internal builds, I've noticed that it either works great or not at all. I've had no problems with 2485 here (other than the to-be-expected things), even my Sound Blaster Live works fine....
Adrian
Hey guys... I have been keeping up fairly much with all the latest builds but I have a question for people who have build 2485 installed and cracked. I just downloaded 2485 and there are 3 cracks out for it. Which one did you guys successfully use? Thanks in advance. As far as I know there is: 2485_Solarixpatch.zip, crack2485.rar and xp2485crackinstall.HackerSp0rtZ.zip.
-Joey
-Joey
Hey there... build 2486 has been out for a few days now. If you have 2485 then there is no need to upgrade since the only thing that was changed was an updated Windows Messenger basically. A new build should be out soon though and RC1 is coming in about 2 weeks. 2485 was an internal build which is why another build was released so soon after it. That doesn't mean 2485 was bad though... Microsoft just released the version to internal people and then released a build soon after for the public since final testing b4 RC1 has to be done and checked.
-Joey
-Joey
