http://www.uploadhouse.com/fileuploads/723/72351130489853223fc44b3ae59f4...
i got that message when trying to work it on Win 2000
any advice ?
thanks
edit : i don't know where is that log file .. so if you need it please tell me where to get it ?
New: Kanri (Oct 09, 2024), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads November!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I think you need the patch. Check right on the Suite page for the 1.0 to 1.0.1 patch.
thanks so much ,, i don't know how i missed reading that part ..
it's working fine now
thanks again
--
Thanks
Amebaid ..
i get that problem all the time with Win2K but i havent been able to get the patch. at first i thought it was an issue with DirectX so when i still had my own internet connection i got DX 8.1 but that didnt solve it so it has to be the patch.
Zoop
if you go to controll panel and click on administrative tools, then go to event viewer and then programs or errors it will display by notifications and errors.
(a little note thogh, 2000 takes a little while before it creates the log so if you wish to view it you will have to wait untuill the popup says OK and not CANCEL.)
Zoop
What does DirectX have to do with patching PAM?
The developer formerly known as ZGitRDun8705
Anything can happen. (DirectX has nothing to do with the PAM ;))
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook
if you knew that DX is the entire interface of windows (basically MS-DOS) that the pam would not work if it could not interface or communicate with DX corectly. and i DO know that directx is how windows communicates with everything, i HAVE asked microsoft about what directx is and i HAVE reserched it. it is very unlikely but directx could have been the problem because every time you use a program or anythign in windows, windows controlls directx and DX controlls the hardware. another reason i know that this is true is because after i upgraded to DX8.1, i kept getting popups from DX telling me that it could not find any DX compatable cd burners - which is bull because the cd burner i had worked with 6.0 through 8.1 with win2k and XP.
Zoop
i do have some wierd and sometimes unbelieveable things happen, i am not crazy or anything. if i had to pull a percentage out of my head i would say that 75% of my problems are also problems of the majority of the people that submit cases to microsoft and the other 25% are problems that i havent diagnosed properly or are little known.
so, anything can happen but that doesent mean it has or will.
**Edit** i didnt say that directx had anything to do with the patch, i meant that in contrary to the patch, it may have been DirectX.
Zoop