Well I am not going to start the recurrent thread of, "why can't I use SoftIce with". . .[you fill the blank]

After I burned my pet computer CPU, Windows XP refused to load with the new CPU. I tried to reinstall WinXP, but you know how those things go. . .
between the updates already installed and the drivers the original install tried to put, it literally fucked up my system.

The new reinstall refused to recognize all my hardware, and after sweating a little, I decided to give a go to the new Win 2003 server OS.

it went sweet, recognized all the hardware, no lag, very sharp very error free OS.

I installed one by one all my apps, no problem.
Installed SoftIce (DS 3.2), cross fingers, YEEEEAH, it worked,
Installed IceExt, the typical problems, a little tweeking, IceExt going, up and running.

Came the windows update, Server 2003 SP1. Why not?

Fuck. SoftIce now gets an error in the NTOSKRNL when it loads, IRQ_LESS_OR EQUAL, BSOD. Uninstalled SP1, but now the display driver is incompatible with Sice, complains it does not support directdraw. Fuck, it was working with the same one before!!!

Try to install Sice inside a VMWare, no problem except Sice interface window does not show. . .

I reinstalled a small winXP OS in a new partition, and Sice and VMware and every body works fine.

Moral,

Server 2003 looks good as an OS. fast, slim. Sice sucks in it.
I do not have the expertise to sort out all the problems, and perhaps Cware does not care. . .

The SP1 version of NTOSKRNL sends Sice to oblivion

The Video display processes (IT IS NOT THE DRIVER it works fine in XP) does not allow Sice to display its universal window.

You have been warned

Just curious, I know there would be driver issues and the such, but did you try transfering your old hard-drive to the new machine - (the smokey smell will disappear eventually) - the meltdown really shouldn't have affected it - any thing left open could easily be repaired using chkdsk.

SiGiNT

I'm waiting for responses on this board blaming Microsoft for one of the following:
"Microsoft is stupid and doesn't know how to make other companies' drivers work in Windows."
"Microsoft is evil and purposely broke SoftICE so that DRM can't be broken."

Mark my word... such responses are on their way

@ sigInt: As far as I can tell, the old hard-drives work fine. and there were no big file errors. The old hard-drive was "transferred" to the new machine, Rather the new machine, MB and CPU were transferred to the old Hard-drive. but WXP was not happy with the new hardware. I tried to repair the install, but then a lot of the device dirvers went out of comission, so I started in clean slate.

@disavowed: You remember the blues when winXP came along, Sice took 2-3 years to catch up. It is not MS fault, I can only blame myself, and perhaps Compuware; Compuware DS only claims to be compatible with win 2003 up to SP1 beta. Sice worked seamlessly in W2003 before the service pack was applied. I think is up to Cware to update Sice to be able to work with the new win SP1.

MS moving the floor from under Sice? no, that would never happen, it would be anticompetitive behavoir.

Update:

1.A clean install restores Sice functionality, as long as SP1 is not installed
2. Win2003 is a server app. Does SoftIce NEED to work in this environment?

I would say yes, because Server software developers need to write specific drivers for win2003 environment. If I had a little more time I would dig more into what exactly is SP1 conflict with Sice. Probably the enhanced security conflicts with Sice.sys over-reaching