Don't buy WinRT if you can use the free version.

We have updated the WinRt download page (http://www.netvigilance.com/winrt) to make it clearer for users to see and understand the difference between the paid version and the free version.

Explained the difference between RT and winRT, and put a little seperation between the paid version's link and the free version's link, to avoid people paying when they only really need the free version.

Still supporting WinRT Actively ?

Mario from US ask :

Do you guys still support WinRT actively? I took a look at the blog site and I haven't seen activity in nearly a year ?



Answer :

We never intended to give free Support on WinRT, but some of the questions was just too lame to leave unanswered (what is default username and password - hint see 1st entry in the blog). And Since the questions got more and more specific and less general in Nature we must refer them all to Paid support.

Mario that goes for your specific question too.

So Yes we very much still support WinRT through PAID Support.

Please see http://www.netvigilance.com/winrt-supportplans for pricing and options.

Please order your PAID support on sales [ at ] netvigilance [dot] com

Regards

JJ

Win 2003 Insufficient Memory

Dave from Melbourne reported that he would get an "Insufficient Memory" error message when install WinRT on Win2003 with 2GB of Ram.

Early investigation showed that the problem did not appear in Windows XP with 2GB.

The problem did also not appear on Win 2003 with 1.5GB Ram and 2Gb of Swap file.

The problem was located in Install shield.

the biggest type in InstallShield is "Number", max size is 2,147,483,647

This means that Installshield cannot correctly handle the amount of memory in Dave's computer without having an Owerflow.

We have coded around the Overflow and the Currently released WinRT 3.4.5 can install on Windows 2003 Server with 2GB of Ram. :-)

Regards

Jesper Jurcenoks
www.netvigilance.com

WinRT Upgrading Version

Many people ask :

What is the difference between the "Free" and the "Commercial" version of WinRT.


Currently there is only one difference.

The commercial version will Upgrade an existing WinRT 3.0.16 installation to WinRT 3.4.5 and Retain all Tickets.

You cannot install the Free version on top of the WinRT 3.0.16, you have to uninstall 3.0.16 first.

We have had some problems with when running WinRt Upgrading version from other drives than the drive where WinRt was installed. A New version fixing this problem has been uploaded.

Best Regards

Jesper Jurcenoks
www.netvigilance.com

Can I become a reseller of WinRT ?

Kigunda from Kenya Asks :

Can I become a reseller of WinRT ?

Answer :

RT Is released in GNU GPL Version 2, which states : (oversimplified)

"You may charge a fee for the physical act of transferring a copy" this means between $5 and $25 to send somebody a CD-rom.

But at the same time those who receive the cd-rom can make a copy and give it to whom they wish.

WinRT is a derired product of RT, and must therefore also be in GNU GPL Version 2.

This is why we are giving away WinRT for Free and why the Source to winRt with our modifications are freely downloadable.

We have made a Special Installer why is not a derived work of RT, and which is closed source.

In this installer we have our proprietary code that allows upgrades from earlier versions of WinRT to the latest version. As the Setup and upgrade code is not covered by GNU GPL V.2 we are able to charge for this extra feature.

As we currently only charge $249 for this upgrade the is not enough margin to make it worth while to insert a reseller between us and the end-user.

This however does not mean that you cannot make money on WinRT.

1) Feel free to buy our commercial version of WinRT and sell it at any profit you like. :-)
Be aware that some customer feel cheated when they realise that they could have purchased the program directly from us at a lower price.

2) Resell our Support plans and Installation Support, or incident support to your customers.
Once you show us the business we will give you a margin that if worth your while.

3) Build your own Expertise in WinRT, and resell it to your customers. Sell your own support plans and installation support.

4) Make costum designed additional features to WinRT or customer modifications specific to your customers, note that under GNU GPL you might have to release your modifications as Open Source under GNU GPL.

I hope this helped,

Best Regards

Jesper Jurcenoks
netVigilance, Inc

Removing TabbedUI

Dear Users of WinRT,

IWe have been forced to remove TabbedUI from the latest version of WinRT, TabbedUI is not part of Best Practicals Distribution of RT, and it is not being kept up to date. as a result we have been shipping a version of WinRT with a faulty TabbedUI.

After Investigating the problems in the TabbedUI we have decided to remove the TabbedUI for now.

netVigilances commitment to WinRT is to Port and Support RT on Windows.

A basis for this is a strong and robust version of RT on Linux/Unix,
Best Practical is doing a fine job with the main Request Tracker, but TabbedI is not as Robust as the rest of the products, therefore it must go.

WinRT dated November 16 2006 and later will not contain TabbedUI

We are currently working on some Compatibility issues that have been reported to us, and once they are fixed, we will continue porting the Current version from Best Practical to windows.
Best Regards

Jesper Jurcenoks
netvigilance, Inc

Customize WinRT

Jim from New Hamshire writes :

Hello,

We have been testing your version of winrt for the past few weeks (with great success so far).

My question is this. It seems all the support info/docs on the internet for RT refer to the RT_SiteConfig.pm file to make any changes or to customize RT (assuming the Linux variety).

It seems that this doesn't work with the Windows version that you provide. Can you point me in the right direction of what files in what directories we would make our changes that would be the equivalent of modifying the RT_SiteConfig.pm?

I have been able to change the logo by modifying the file:

C:\Program Files\SecureScout\RequestTracker\rt\html\Elements\Header

but beyond this, I am lost.

Thanks for your time..

Answer :

hi Jim.

The file you are looking for is called Rt_Config.pm the name was changed on the linux version of RT some time back.

on WinRt you can find it in :

C:\Program Files\SecureScout\Request Tracker\winrt\conf\RT_Config.pm

when you change this file make sure you completely stop Apache before restarting it, a simple restart will typically not pick up the changes.

Regards

WinRt Support.
Jesper Jurcenoks
www.netvigilance.com

Deleting Tickets

Ashok from Bangalore writes :

"I login as root... I haven't been able to figure out how I can delete a ticket.... root is a super user and has all priviledges and rights...however when I click on any ticket I get oly the following options.. 'Take' 'Reply' 'Comment'

noting to delete ...how to set this right ?"

Ashok rates this as Severity :"A major feature is broken"

Answer :

1) We don't make RT, we only port it to Windows, any complains on design and usability must be taken to Best Practical.
2) Tickets are not meant to be deleted as part of the normal workflow this is the reason for you not having a delete option. Per definition Ticket are closed and stayes in the system for Audit purposes.
3) to delete a ticket click "Reply", "Resolve" or "Comment", change status to "Deleted" - click "Update Ticket"

Regards

WinRT Support.