I'll see what I can do but troubleshooting this via the forum is going to be 10x pain in the butt.
What kind of Stop code are you getting, and at what point in the boot process does it happen (what's on the screen at the time). If it's like a 7B or something it's probably unrelated to your sybase - just got unlucky you had a crash while installing.
A quick shot-in-the-dark fix:
from recovery console use ListSvc to get a list of the drivers and services that are starting. Find any sybase related services and use the disable command to shut them down. Be sure to take notes - you'll need to know their startup type (boot, system, auto) when you go to reenable.
If that doesn't do it, then do this:
make a backup copy of the SYSTEM and SOFTWARE files in your system32\config folder.
Then copy over the same files from your windows\repair folder.
Reboot.
This should let you boot, but don't get excited. Those are likely some really old hives you are running. You may have to install a nic driver or some other contortions. Once you are up, get a zipped copy of the system and software files you backed up (the bad ones) and get them to me. I'll PM you my email address. If you disabled anything per the steps above, be sure to send me the details.
Armed with the details of your stop code and your hives I'll document the changes I make and send em back to you. If dropping your repair hives doesn't get you going then you've likely got some damaged system32 or system32\drivers files, or sybase inserted a goofy driver or something. We'll cross that bridge if we have to.
If you gotta get this going asap, you might want to give MS tech support a ring and ask for their "Setup" team. I'm ex-Setup and those guys will definately get you booting again.
Facebook
Twitter