SC didn't likely do the damage...something else..... OLEDB connections may be hitting stack overflow due to sp's called on connection (e.g. sp_mda). Look in master..sysdevices for where the device physical paths are and make sure they are there. If so, try sp_who and see if someone in log suspend (kills will hang if log suspend as it will attempt to rollback). If it created SERVERNAME.142, then SERVERNAME.cfg is there - or you can force it to write a new one with sp_configure - haven't done it in a while, so forget the syntax, but doc shows syntax of:
sp_configure "configuration file", 0, {"write" | "read" | "verify" | "restore"}, "file_name"
WRT to attaching with shared memory - the files *should* be in %SYBASE%/ASE-15_0 - should be SERVERNAME.krg and one or more SERVERNAME.sr# where # is a number from 0-n