Hi Alcino,
Does your older boot sequence in the log show some other license normally getting checked out as the next thing after checking out ASE_ASM? Or does it proceed to show a "kernel memory" allocation next?
If it looks like a license might be next, there might be some error in the SYSAM log
in $SYBASE\SYSAM-2_0\log
I'm not greatly knowledgable on Windows. For memory issues on a UNIX platform I'd start by looking at "ipcs -m" to see what was already out there for allocated shared memory. On Windows, I think you can monitor memory by starting up the Task Manager, under the Permformance tab is a "resource monitor" button which takes you to a screen with a memory tab. That might show if there is something out there hogging memory.
You could also try modifying the configuration file (perhaps just copying in an older version) just to see if the server would boot if it had much lower memory requirements. (that isn't meant as a solution, just a diagnostic step. You presumably don't want to go into production with the configurations set to a minimal state).
And you might look at the recent configuration files to see if there were any major changes since the last time ASE booted.
-bret