I still couldn't pinpoint the exact thing (or things) that enabled the SDK to work on VISTA yet, while on numerous occasions in the past it had not even initiated.
However, I can tell my set up situation which may be helpful if one thinks that it'd be worth replicating or finding clues in it:
1- SYSTEM
I use VISTA Ultimate 32 bit Service Pack 1 installed
3 Gig RAM, ASUS motherboard, Intel CPU (pentium D 3.41GFHz)
Nvidia 178.24 drivers
ZoneAlarmPro and Kasperksy2009 always running
Zone Alarm Pro -OS Firewall and program interaction control is ON
2- Services, processes
I recently shot down a couple of services, which I can't remember the full list (maybe it was the factor)
I shut down the service of Windows Defender (previously it was only turned off)
UAC is turned off
Also some remote registry and all that risky stuff are off
3-How I proceeded
--Installed SDK normally
-- Started
createDiskX Batch file (find it in X-Ray SDK\scripts_plugins)
--Made
shortcuts to
Map X-Drive (X-Ray SDK\scripts_plugins -or find it in windows programs), and the
Batch files of
Actor_Editor, Level_Editor, Particle_Editor (find them in Xray SDK\ Level Editor folder) by right clicking and sending them to desktop as shortcuts -very simple.
--Before each start of SDK,
you should MAP the X-DRIVE--I started the Level_Editor through its
Batch File shortcut...
NOT by its
start icon in the folder.
**DO NOT try to open an image/object by "open with SDK\Level Editor, or, Particle Editor, etc. It'll crash, giving "can't open fs.ltx" Start the Editor first by the Batch file. You should have placed the file that you want to work on into a separate folder that you would navigate to later, or simply put in in "import" (level_editor\import) folder.
--I started the program as above, at this point, (AN IMPORTANT POINT?) ZoneAlarmPro's OS Firewall raised a pop up (dialog window) and informed me that SDK is trying get into Windows resources and attempts use this and that process and services. I said YES. (ZoneAlarm checks every program’s each behaviour and its any moves to use any other programs' or Window's any components, services, etc. I keep it on manual)
NOTE: ZoneAlarm previously had not asked this. Maybe it was one of the services that I closed helped SDK to pass an hurdle and then ZoneAlarm grabbed it. I think it may (just may) be possible that after I said YES to Zone Alarm OS Firewall, it has actively initiated and tied the SDK to some resources otherwise it had not been successful itself to reach. From that point onwards, SDK on VISTA is working flawlessly as it may seen in the already produced "crashed and torn missile damaged APCs"
viewtopic.php?f=2&t=3&start=738If I can remember or be able to point a more specific or additional factors, I'll again update this thread.