Jordan Russell mentioned problems with original versions of Windows 95 and
Delphi 6. These are an unofficial, unsupported options, since Windows 95 is an
unsupported OS for Delphi 6.
Anyway, here's your options:
1. Install the Win95 DCOM 1.2 Service pack on those machines that have not
been touched at all since Windows 95 initially shipped.
2. Change the following code in Variants.pas to look like this:
procedure NotViaOS(var Dest: TVarData);
begin
// VarResultCheck(VarNot(Dest, Dest));
end;
procedure NegateViaOS(var Dest: TVarData);
begin
// VarResultCheck(VarNeg(Dest, Dest));
end;
Then include Variants.pas in your project and build without packages.
This should remove any dependencies. All the other string conversion routines
in VarUtils are already available in the original Win95. That includes these
from VarUtils:
function VarI4FromStr(const strIn: WideString; LCID: Integer; dwFlags:
Longint;
out lOut: Longint): HResult; stdcall;
function VarR8FromStr(const strIn: WideString; LCID: Integer; dwFlags:
Longint;
out dblOut: Double): HResult; stdcall;
function VarDateFromStr(const strIn: WideString; lcid: DWORD; dwFlags:
Longint;
out dateOut: TDateTime): HRESULT; stdcall;
function VarCyFromStr(const strIn: WideString; lcid: DWORD; dwFlags: Longint;
out cyOut: Currency): HRESULT; stdcall;
function VarBoolFromStr(const strIn: WideString; LCID: Integer; dwFlags:
Longint;
out boolOut: WordBool): HResult; stdcall;
function VarBstrFromCy(cyIn: Currency; LCID: Integer; dwFlags: Longint;
out bstrOut: WideString): HResult; stdcall;
function VarBstrFromDate(dateIn: TDateTime; LCID: Integer; dwFlags: Longint;
out bstrOut: WideString): HResult; stdcall;
function VarBstrFromBool(boolIn: WordBool; LCID: Integer; dwFlags: Longint;
out bstrOut: WideString): HResult; stdcall;
--
John Kaster, Borland Developer Relations, http://community.borland.com
$1280/$50K: Thanks to my donors!
http://homepages.borland.com/jkaster/tnt/thanks.html
Buy Kylix! http://www.borland.com/kylix * Got source?
http://codecentral.borland.com
The #1 Java IDE: http://www.borland.com/jbuilder
> Jordan Russell mentioned problems with original versions of Windows 95 and
> Delphi 6. These are an unofficial, unsupported options, since Windows 95
is an
> unsupported OS for Delphi 6
That was quick! Clap clap!
Regards,
Alessandro Federici
PS: Now can you take a look at my TP 3.02 bug report of 1989? (<---- just
joking!!!)
I'm curious: Is that allowed ?
If so, it means that component builders can also use some of the Delphi dfm
files in the sources directory, right?
Stephan Marais
Use - yes, distribute - no. This can in some instances cause problems like with
the personal edition that comes with no source and therefor might not even have
the dfm found in the source directory. You have always had the right to modify
for your own use the source in the source directories. You may not distribute
those changed files (you may distribute the instructions on how to change the
files, but not the changed files themselves) nor may you build new packages with
the same name as the Borland supplied packages with your changed VCL.
>
> Stephan Marais
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
This sad little lizard told me that he was a brontosaurus on his mother's
side. I did not laugh; people who boast of ancestry often have little else
to sustain them. Humoring them costs nothing and ads to happiness in
a world in which happiness is in short supply. (RAH)
--
John M. Jacobson
Visit Jake's Delphi Page at http://www.xnet.com/~johnjac
"Oh, no! She's stuck in an infinite loop, and he's an idiot. Oh well,
that's love for you."
-Professor Farnsworth in "Futurama"
"John Kaster (Borland)" <jka...@borland.com> wrote in message
news:3C744D2D...@borland.com...
Hmm, commenting out code makes me a bit uneasy. :)
Is there a reason why Variants.pas can't just be replaced with the
Variants.pas from D6U1? Are other units in D6U2 dependent on the new
Variants.pas?
--
Jordan Russell
The number of changes for Variants.pas between UP1 and UP2 were significant.
Variants.pas in UP1 was broken in a lot of places. I'm sure there are several
changes in UP2 that expect the correct behavior of the Variants.pas in Up2 and
not the incorrect behavior in UP1.
>
> --
> Jordan Russell
Simply time management. I thought I might be able to get a resolution in less
time than it would take to answer the same question over and over.
"John Kaster (Borland)" <jka...@borland.com> wrote in message
news:3C744D2D...@borland.com...
There should also be some significant performance gains in the new version.
No kidding....
<STANDING OVATION! />
Tony Caduto
Milwaukee WI
...Michael...
"John Kaster (Borland)" <jka...@borland.com> wrote in message
news:3C744D2D...@borland.com...
>Moved this up to increase its visibility:
>
>Jordan Russell mentioned problems with original versions of Windows 95 and
>Delphi 6. These are an unofficial, unsupported options, since Windows 95 is an
>unsupported OS for Delphi 6.
>
>Anyway, here's your options:
what about users of D& personal that cannot alter source code?
Bye
Kirys
--------------------------------------------------
Kirys
Remove REMOVETHIS to reply
Shouldn't that be
<OVATION Kind="STANDING" /> ? :^)
Cheerio
Radek, looking at the world through XML Glasses.
Thanks for the quick response.
Anyone has any idea what implications uncommenting this code has? As far
as I can see it these methods are only called for unknown OLE objects
(like IInterface or IUnknown interface pointer according to the Delphi
help file). It seems that for these kind of objects NOT or NEG don't
have a meaning at all. Am I right???
JD
Tony,
Try i.e not IE - Bill will want licensing fees for the use of his IE ;-)
I don't think the issue is that many or any of Borland's customers are
running Win95 for development.
The issue is that programs created with Delphi still need to run on
Win95. A lot of business users (ie *our* customer's not Borland's) are
still running Win95 - crazy or otherwise - and many of us (myself
included) need to be able to write programs that they can run.
I can't say to my business customers "here's my app that will cost you
5000 pounds - oh and by the way you need to upgrade all your systems
to xxx for just half a million".
I wonder how many potential purchasers of your newsreader will still
be running Win95? :-)
Steve
>Jordan Russell mentioned problems with original versions of Windows 95 and
>Delphi 6. These are an unofficial, unsupported options, since Windows 95 is an
>unsupported OS for Delphi 6.
Thanks. Now I'll go off and get that SP2 and see how it goes...
Steve
> The issue is that programs created with Delphi still need to run on
> Win95. A lot of business users (ie *our* customer's not Borland's) are
> still running Win95 - crazy or otherwise - and many of us (myself
> included) need to be able to write programs that they can run.
To the point.
I on my side am not critizing Borland for this at all, most of us
have earlier versions of Delphi that can be used. The thing is that
some Delphi users may get an unpleasant surprise.
Ingvar Nilsen
Excellent! Nice job John. Wise man too.
David R.
They can't redistribute apps either, so the issue is a lot smaller. Win95 is after all
unsupported.
--
Anders Ohlsson - Borland Developer Relations - http://community.borland.com/
Come to Anaheim! Best BorCon ever! - http://www.borland.com/conf2002/
Get the #1 Java IDE! - http://www.borland.com/jbuilder/
Get Kylix now! - http://www.borland.com/kylix/
Cycling to cure cancer - http://homepages.borland.com/jkaster/tnt/
http://homepages.borland.com/aohlsson/disclaimer_ani.gif
> Does this apply to apps that don't use variants?
Any program that uses the Classes unit (which includes all programs that
use forms, data modules, etc.) pull in the Variants unit, which loads
oleaut32.dll. This happens even if you don't use Variants in your program.
The problem is that the program doesn't know whether a DFM will have a
Variant property value stored in it, so the DFM streaming system always has
the Variant-reading code linked in.
--
Ray Lischner, author of Delphi in a Nutshell
http://www.tempest-sw.com/
> Anyone has any idea what implications uncommenting this code has? As far
> as I can see it these methods are only called for unknown OLE objects
> (like IInterface or IUnknown interface pointer according to the Delphi
> help file). It seems that for these kind of objects NOT or NEG don't
> have a meaning at all. Am I right???
You are correct. So don't use the hacked Variants.pas for a program that
uses SOAP, Corba, COM, etc.
> 2. Change the following code in Variants.pas to look like this:
...
> Then include Variants.pas in your project and build without packages.
Another approach doesn't involve changing the source code. Add VarUtils.pas
to the project, and compile with GenericOperations defined in the project
options.
--
David Marcus
Tony
"Greg Bielleman" <gbie...@NoSpam.bigpond.net.au> wrote in message
news:3c74d589_1@dnews...
On Wed, 20 Feb 2002 20:11:26 -0800, "John Kaster (Borland)"
<jka...@borland.com> wrote:
>There should also be some significant performance gains in the new version.
Naturally, if you have to comment out code <gd&r>
Cheers, Julian
-----------------------------------------------------------
Julian M Bucknall
nospam...@turbopower.com (delete nospam)
TurboPower Software Company - www.turbopower.com
Personal - www.boyet.com, www.home.turbopower.com/~julianb
Author of "Tomes of Delphi: Algorithms and Data Structures"
Read Algorithms Alfresco in The Delphi Magazine every month
-----------------------------------------------------------
<smack!> (As in, with a trout, not a kiss.)
Should I care about writing DOS applications or Win 3.1 apps or the old
Win95? If people still use it, it's their problem not Borland's
People should move on!!
To new stuff
Steve Gouldstone <st...@langdaledesigns.co.uk> wrote in message
news:lgn97u41te3jpbh7n...@4ax.com...
I'd like to see your customers' reactions when you tell them that...
> Should I care about writing DOS applications or Win 3.1 apps or the old
> Win95? If people still use it, it's their problem not Borland's
Again, it's not so much a problem that Borland decided to quit "certifying"
Windows 95, it's that Windows 95 support was forcefully removed in a
*patch*.
--
Jordan Russell
Hi,
> Again, it's not so much a problem that Borland decided to quit "certifying"
> Windows 95, it's that Windows 95 support was forcefully removed in a
> *patch*.
How can support for Win95 be removed, when D6 did not support Win95 in
the first place? The fact that some apps compiled with D6 worked on
Win95, was more down to luck than anything else.
J
> How can support for Win95 be removed, when D6 did not support Win95 in
> the first place?
Fact: D6 apps ran without any problems on Windows 95, they did not after
SP2.
> The fact that some apps compiled with D6 worked on
> Win95, was more down to luck than anything else.
No, it was good old Borland engineering. By creating a great VCL it hold
for a long time even without certification.
JD
--
John M. Jacobson
Visit Jake's Delphi Page at http://www.xnet.com/~johnjac
"Oh, no! She's stuck in an infinite loop, and he's an idiot. Oh well,
that's love for you."
-Professor Farnsworth in "Futurama"
"Steve Gouldstone" <st...@langdaledesigns.co.uk> wrote in message
news:lgn97u41te3jpbh7n...@4ax.com...
That'll be the geeks only newsreader then <g>. I assume it will also run
on XP. It's probably a good idea to let the installer prevent
installations on Win9x platforms.
JD
>That'll be the geeks only newsreader then <g>. I assume it will also run
>on XP. It's probably a good idea to let the installer prevent
>installations on Win9x platforms.
Yep. It is being designed for power users.
***Posted by Jake's Custom Newsgroup Reader***
I stand corrected.
I think you're remembering the academic license, which prohibits transmission
to others, except other academic licensees.
--
-Brion
Team JEDI, 2001 Spirit of Delphi Award Winners
http://www.delphi-jedi.org
Fresno Area Delphi Users Group
http://groups.yahoo.com/group/FresnoDelphi