IWBasic v2

[Brian]

Hi,

What kind of cost are you projecting for IWasic v2? Just the cost for a one-off, not an upgrade, etc

Brian

[Rock Ridge Farm (Larry)]

Have not decided.
I am looking at $69.95 but I would really like it to be $49.95.
At the $49.95 price and the fact that almost everyone got stuck with one of the deals in the past
would mean after the discount there would be such a small return on the time and effort
that went into it - it would not be cost effective.
2.0 is not a small upgrade but a major re-structure and enhancement.
The 3 of us on the dev team put in hundreds of hours to build it.

IW made a profit of $429.00  last year - part of that was owed to Larry Mc
for Designer sales - he and I decided to invest that profit in a software package
to make a much better documentation package for V2.

The profit could have been much higher but I have tried to work out something
with the previous 'deal' holders (I was one of those as well).

I still had several people who were not happy and thought that I should honor the
'deals' made by the PO. This is not practical.

V2 will be the last time I do any of this.

IW policy going forward:
1. No product will be sold as a pre-release.
2. No request for the customers to fund future development will ever be made.
3. No form of request for you the members/customers to pay for anything outside of products will be made.
4. We will price each major release stand-alone. A major release will have enough change/enhancment to justify a release. (64 bit would be a major release)
5. Bug fixes will be free (point issues).

I welcome your comments and suggestions - I do not do this to get rich - just for fun.
I need to pay the IW related bills and meet my profit share agreements with the dev team.
This will determine the cost of products in the future.

Probably a lot more than you ask - but it needs to be communicated.

Larry

[Brian]

Larry,

Sounds good to me, and a fuller explanation than I reckoned on!

Like you, I program for fun. I have never been paid anything at all for any
program I have produced. Just thanks!

Brian

[Barney]

Thank you for the good news. I am glad v2 is so near the release date and my credit card is ready. $69.95 sounds good to me but I agree that $49.95 is better, not only because it is cheaper but mostly because it is under the psychological barrier of $50. Quite important for a lot of customers. I am also glad you decided to drop all of the old kind of deals. Each full new version should be full price with a certain reduction in price for owners of previous version. That approach works quite well for PowerBasic and other similar products. I see no reason why it should not work for IWBasic, as well.

Barney

[AdrianFox]

Just to add my 4 penny worth, I understand the need for a decent return on all the hard work that has been done, and to keep this forum and language alive,  but I would find it hard to justify $69.95 to my wife, but I might just get away with $49.95!   

Seriously, there is a law of diminishing returns and I think just under $50 works whereas just under $70 doesn't!

[mrainey]

My wife and I have agreed on a "don't ask don't tell" policy.   

[LarryMc]

My wife and I have agreed on a "don't ask don't tell" policy.   

Oh... I see.

you don't tell her and pray that she don't ask....

LarryMc

[Logman]

Compared to what parts for my airplane cost, $69 would be a piece of good news to my wife.

Logman 

[Bruce Peaslee]

$69 is not so far from $49. There is the reverse to think about as well: charging too little might make some folks think nothing went into its development.

[Doc]

Along the same lines as what Bruce mentioned...
If it's worth $69.00 then by all means price it that way. Should you decide to offer an upgrade policy (competitive upgrade or otherwise), that would be altogether a different decision and "perk" for established customers, but the actual value of the product is what it is, IMO.

Just my 2Ã,¢ worth, and yes, I'd like to have my change back.

-Doc-

[barry]

The profit could have been much higher but I have tried to work out something
with the previous 'deal' holders (I was one of those as well).

I still had several people who were not happy and thought that I should honor the
'deals' made by the PO. This is not practical.

V2 will be the last time I do any of this.

IW policy going forward:
1. No product will be sold as a pre-release.
2. No request for the customers to fund future development will ever be made.
3. No form of request for you the members/customers to pay for anything outside of products will be made.
4. We will price each major release stand-alone. A major release will have enough change/enhancment to justify a release. (64 bit would be a major release)
5. Bug fixes will be free (point issues).

I welcome your comments and suggestions - I do not do this to get rich - just for fun.
I need to pay the IW related bills and meet my profit share agreements with the dev team.
This will determine the cost of products in the future.

I spent quite a bit for things I never got with both IBasic and EBasic.  I'm sure others here did too.  I don't mind too much, looking back.  What I did get was worthwhile, but more than once I felt bad about being left holding the bag.  It's not a nice feeling.

With that in mind I'm glad to see your new policy.  I think it's a good one.

Barry

[tbohon]

I agree with the others here - $69.95 is a fair price for a major upgrade/re-write/release and I think that at least this first time everybody should pay that to try and help the dev team recoup their expenses (yes, time is money, trust me ... )

Good idea, good plan - let's go for it!!!

[newuser]

Have not decided.
I am looking at $69.95 but I would really like it to be $49.95.
At the $49.95 price and the fact that almost everyone got stuck with one of the deals in the past
would mean after the discount there would be such a small return on the time and effort
that went into it - it would not be cost effective.
2.0 is not a small upgrade but a major re-structure and enhancement.
The 3 of us on the dev team put in hundreds of hours to build it.

IW made a profit of $429.00  last year - part of that was owed to Larry Mc
for Designer sales - he and I decided to invest that profit in a software package
to make a much better documentation package for V2.

The profit could have been much higher but I have tried to work out something
with the previous 'deal' holders (I was one of those as well).

I still had several people who were not happy and thought that I should honor the
'deals' made by the PO. This is not practical.

V2 will be the last time I do any of this.

IW policy going forward:
1. No product will be sold as a pre-release.
2. No request for the customers to fund future development will ever be made.
3. No form of request for you the members/customers to pay for anything outside of products will be made.
4. We will price each major release stand-alone. A major release will have enough change/enhancment to justify a release. (64 bit would be a major release)
5. Bug fixes will be free (point issues).

I welcome your comments and suggestions - I do not do this to get rich - just for fun.
I need to pay the IW related bills and meet my profit share agreements with the dev team.
This will determine the cost of products in the future.

Probably a lot more than you ask - but it needs to be communicated.

Larry

One question here, since version 2.0 have just been released, a major release means 2.x(example  2.1, 2.5, 2.8..)or
means a total new version like v3.0(3.1, 3.5, a big leap from version 2 to version 3) onwards beside a 64bit version release?

[LarryMc]

Ver 2.0 hasn't been released quite yet.

Major Releases are 2.0, 3.0, 4.0 etc.
64 bit will probably be a major release, when ever it comes.

LarryMc

[Barney]

Well, the new IW2 looks very, very nice.
I quite enjoy  it.

And since this forum is restored it looks like it is time to purchase it.
Will there be an official announcement?

I am running it on Win7 64-bits and the only thing I don't like is the UAC message popping up every time I start IWBasic. Easy to circumvent but it would be better if the circumvention is not needed.

Barney

[aurelCB]

I dont know how look on win7 but on winXP it looks that manifest not work.

[WayneA]

I look forward to buying this semi shortly (couple weeks)

Woot, looks great.

[obelisk]

Hi

I just installed v2 and tried to compile a  previous project. I get many errors.


File: ebstd.incc (107) Error: duplicate declaration of MILLISECS
File: C:\Program Files\iwbdev\bin\iwbstd.incc (109) See previous declaration
File: ebstd.incc (109) Error: duplicate declaration of CoInitialize
File: C:\Program Files\iwbdev\bin\iwbstd.incc (111) See previous declaration
File: ebstd.incc (110) Error: duplicate declaration of CoUninitialize
File: C:\Program Files\iwbdev\bin\iwbstd.incc (112) See previous declaration
File: ebstd.incc (111) Error: duplicate declaration of CoCreateInstance
File: C:\Program Files\iwbdev\bin\iwbstd.incc (113) See previous declaration
File: ebstd.incc (113) Error: syntax error - ABS
File: ebstd.incc (114) Error: syntax error - ACOS
File: ebstd.incc (115) Error: syntax error - FACOS
File: ebstd.incc (116) Error: syntax error - ACOSD
File: ebstd.incc (117) Error: syntax error - FACOSD
File: ebstd.incc (118) Error: syntax error - ALLOCMEM
File: ebstd.incc (119) Error: syntax error - APPEND$
...

What am I doing wrong?

[LarryMc]

You installed it in the same folder that EBasic or IWBasic 1.8 was installed in.

Install it into an empty folder and your problems should go away.

LarryMc

[obelisk]

Thank you for the quick response
It worked

[Guilect]

What am I doing wrong?

I have successfully compiled other samples in V2.0 but am getting errors with this.
From out of the help files I got this code:

Code Select Expand

openconsole

int a = 0

'int a = 1

WHILE 1

  TRY

    print 1/a

    print "success"

    BREAK

  ENDTRY

  print "Divide by Zero Error- Using default"

  a=1

ENDWHILE



print "Any key to end"

waitcon

closeconsole

end
Then get these errors:

Compiling...
IWBASIC1.iwb
No Errors

Linking...
IWBasicLinker v1.12 Copyright ÂÃ,© 2009,2010 Ionic Wind Software
Error: Bad COFF symbol location for E:\basic\iwbdev\libs\iwbstd.lib
Error: Error loading library module from file E:\basic\iwbdev\libs\iwbstd.lib
Error: Bad library E:\basic\iwbdev\libs\iwbstd.lib: Symbol _ebclearexceptionflag in dictionary, but not in specified module

Error(s) in linking E:\basic\iwbdev\IWBASIC1.exe

[LarryMc]

I can remember testing the code I put in the help file and it working.

However, I just tried it and got the same result as you.

Sapero will have to look into it when he gets back on.

Note: I just tried it with an earlier beta of 2.0 I still had on my computer and it worked fine.
It must have gotten broke while fixing some other problem between that beta version and the final release version.
LarryMc

[Logman]

Just purchased licensed version of 2.0. Very nice, and it installed straight forward on 64-bit Windows 7.

Larry, excellent update of the user's manual, I'm impressed by the more thorough explanations and improved code examples.

I compiled a couple of console programs and they worked perfectly so far.

Sapero did an outstanding job updating and adding new features.

Logman

[sapero]

Thanks for reporting! A bugfix is waiting for the admin to upload.

[Barney]

Definitely much better in this version.

I am ready (was always) to buy it but I still wait for the message from Larry regarding the special price for owners of previous versions.

Barney