I considered deleting this thread.
A reply canceled the delete attempt.
This topic is probably (seemingly?) irrelevant to many.
Those that wish to distribute productions made with newer 3DGS versions to individuals using older systems like Win98 SE, WinME, etc. probably won't care either.
The first link is for background purposes?
(No Win98 for 6.60, WHY?)
forum style mentioned:
The instructions were posted using [ code ] [ /code ] tags to preserve formating.
Code area box seems wider than needs to be.
Maybe a smaller font is used on this machine.
The area seems to be about more than 2 times the width needed for the longest string of 'pre' text displayed.
Maybe this is in contrast to other forum style issues mentioned recently.
Quoting Joey.
It is believed, within the 'programming art schools', Joey is an upperclassman.
seriously, i know i'm no native speaker, but i don't understand what you're talking about.
:Sigh:
Thank you, Joey.
We get that a lot, it seems.
It is a 'fault' here.
We do not communicate well.
I think it is supposed to be my 'first language', but often, I feel I'm 'no native speaker' myself.
(Chemical balances, ripping pain from cures seemingly worse than the ailments they treat, bad medicine combinations, ...oh my.
Noises like an animal as I try to leash and redirect pain and energy.
Some moments are better than others.
Communication was difficult before, but now...)
i think the answer is 42.
Humor, intelligence, knowledge, & humility at times...very good.
We have newer & older computers here.
Computers are sometimes referred to as boxes, machines, terminals, stations, systems, units, etc.
One of the older computers, still runs Windows 98 SE.
My son & I still use that old computer, from time to time.
Sometimes, when using the older computer, which runs Windows 98 SE, with (mutilated?) DirectX 9c, my 6 year old son plays with 3DGS toy applications (games or applications made with 3DGS).
3DGS applications 'compiled' with (some) versions after 6.40.5 did not seem to start or start properly on the old machine.
These versions may include: 6.50 (don't use), 6.60 (latest A6?), Lite-C 1.05.5 (free).
(A7 might be included in this list.)
(The appearance of start failures may seem to differ from 6.50 and 6.60.)
It is possible that solutions were offered elsewhere already.
The issues may be faults here (result of bad practices, user error, archaic systems, etc.))
When publishing a project with some post 6.40.5 versions, it seems a file d3x9_30.dll is copied to the project's published folder (.cd?).
The versions above seemed to start on the older system running Win98 SE (mangled?), with DirectX 9c, when that file, d3x9_30.dll, was replaced with a file, d3x9_24.dll, renamed to d3x9_30.dll.
If it seems user licenses were violated during the process, there were no intentions to do so, and if need be, the process did not occur or did not involve any 'known' parties.
Again or not, the relevancy is probably limited to a local scope here, the issues may have been a result of faults here, 'practices' presented may be less than optimal and / or may not be effective elsewhere, etc.
I was asking other parties for information.
parties include:
Conitec staff
users
.dll swap, hm?
Sending computer in the mail, but be a psychic first please.
Why? Why not?
What are the ramifications?
Links please?
DirectX, what's the skinny?
Conitec insight, why not share with this dumb user, please?
Arrogantly slap us with the knowledge / wisdom stick...
The download page is a myth, but myths may contain answers, or maybe not.
Considering the level of physical discomfort (distracting pain), that will have to do.
(Routine of strong internal pain, ulcers, stomach bleeding?...)
It's all probably rather superfluous anyway.