You are not logged in. [Log In] KiXtart.org website » Forums » KiXtart » Lounge » VBSCRIPT end of the Road ahead.
Register User       Forum List       Calendar       FAQ
Page 1 of 1 1
Topic Options
#214269 - 2023-10-11 04:05 PM VBSCRIPT end of the Road ahead.
Allen Administrator Offline
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4562
Loc: USA
Microsoft announced that VBSript will be installed optionally going forward, and eventually be removed from Windows.

https://www.techspot.com/news/100452-microsoft-plans-kill-vbscript-future-windows-releases.html
Top
#214270 - 2023-10-19 10:02 AM Re: VBSCRIPT end of the Road ahead. [Re: Allen]
Arend_ Moderator Offline
MM club member
*****

Registered: 2005-01-17
Posts: 1896
Loc: Hilversum, The Netherlands
Wow, I wonder how they will replace slmgr.vbs then, amongst others.
I did a quick scan of *.vbs on a Windows 11 machine and there are quite a few results from Microsoft itself.

 Code:
C:\Program Files\Microsoft Office\Office16\OSPP.VBS
C:\Windows\System32\gatherNetworkInfo.vbs
C:\Windows\System32\slmgr.vbs
C:\Windows\System32\SyncAppvPublishingServer.vbs
C:\Windows\System32\winrm.vbs
C:\Windows\System32\Printing_Admin_Scripts\en-US\prncnfg.vbs
C:\Windows\System32\Printing_Admin_Scripts\en-US\prndrvr.vbs
C:\Windows\System32\Printing_Admin_Scripts\en-US\prnjobs.vbs
C:\Windows\System32\Printing_Admin_Scripts\en-US\prnmngr.vbs
C:\Windows\System32\Printing_Admin_Scripts\en-US\prnport.vbs
C:\Windows\System32\Printing_Admin_Scripts\en-US\prnqctl.vbs
C:\Windows\System32\Printing_Admin_Scripts\en-US\pubprn.vbs
C:\Windows\SysWOW64\slmgr.vbs
C:\Windows\SysWOW64\winrm.vbs
C:\Windows\SysWOW64\Printing_Admin_Scripts\en-US\prncnfg.vbs
C:\Windows\SysWOW64\Printing_Admin_Scripts\en-US\prndrvr.vbs
C:\Windows\SysWOW64\Printing_Admin_Scripts\en-US\prnjobs.vbs
C:\Windows\SysWOW64\Printing_Admin_Scripts\en-US\prnmngr.vbs
C:\Windows\SysWOW64\Printing_Admin_Scripts\en-US\prnport.vbs
C:\Windows\SysWOW64\Printing_Admin_Scripts\en-US\prnqctl.vbs
C:\Windows\SysWOW64\Printing_Admin_Scripts\en-US\pubprn.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-a..nagement-appvclient_31bf3856ad364e35_10.0.22621.2070_none_ac8a770443970ffe\SyncAppvPublishingServer.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-a..nagement-appvclient_31bf3856ad364e35_10.0.22621.2283_none_ac75931e43a6ae1a\SyncAppvPublishingServer.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_10.0.22621.1_none_dfdc389d6af52efc\adsutil.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_10.0.22621.1_none_dfdc389d6af52efc\IIsExt.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-nettrace-netsh-helper_31bf3856ad364e35_10.0.22621.1_none_fcc32c0b64120b7d\gatherNetworkInfo.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_70432baa400e82bb\prncnfg.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_70432baa400e82bb\prndrvr.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_70432baa400e82bb\prnjobs.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_70432baa400e82bb\prnmngr.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_70432baa400e82bb\prnport.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_70432baa400e82bb\prnqctl.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_70432baa400e82bb\pubprn.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-security-spp-tools_31bf3856ad364e35_10.0.22621.1_none_a72f11d2b2de8e85\slmgr.vbs
C:\Windows\WinSxS\amd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.22621.2070_none_aa7d75492877e03c\winrm.vbs
C:\Windows\WinSxS\wow64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_10.0.22621.1_none_ea30e2ef9f55f0f7\IIsExt.vbs
C:\Windows\WinSxS\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_7a97d5fc746f44b6\prncnfg.vbs
C:\Windows\WinSxS\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_7a97d5fc746f44b6\prndrvr.vbs
C:\Windows\WinSxS\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_7a97d5fc746f44b6\prnjobs.vbs
C:\Windows\WinSxS\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_7a97d5fc746f44b6\prnmngr.vbs
C:\Windows\WinSxS\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_7a97d5fc746f44b6\prnport.vbs
C:\Windows\WinSxS\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_7a97d5fc746f44b6\prnqctl.vbs
C:\Windows\WinSxS\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.22621.1_en-us_7a97d5fc746f44b6\pubprn.vbs
C:\Windows\WinSxS\wow64_microsoft-windows-security-spp-tools_31bf3856ad364e35_10.0.22621.1_none_b183bc24e73f5080\slmgr.vbs
C:\Windows\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.22621.2070_none_b4d21f9b5cd8a237\winrm.vbs

Top
#214271 - 2023-12-16 07:32 PM Re: VBSCRIPT end of the Road ahead. [Re: Arend_]
Allen Administrator Offline
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4562
Loc: USA
In Microsoft's next news of depreciation...

Microsoft deprecates Legacy console mode in Windows 11 and future releases


About Legacy Console mode

Differences between modes
The Console Host team strives to minimize differences between the Legacy and current modes of the console to ensure that as many customers as possible can run the most up-to-date version. If you experience an issue that requires you to use the legacy console that is not documented here, please contact the team on the microsoft/terminal GitHub repository or via the Feedback Hub for assistance.

16-bit applications on 32-bit Windows
Some 16-bit applications on 32-bit Windows use a virtual machine technology to operate called NTVDM. Often these applications use a graphical screen buffering mode in conjunction with the console hosting environment to operate. Only the legacy console experience supports these graphical buffering modes and the additional console API support required to power these applications. The system will automatically select the legacy console environment when one of these applications is launched.

IME Embedding
The legacy Console Host embedded the suggestion portion of the IME inside the hosting window by reserving a line at the bottom of the screen for suggestions. The current Console Host environment instead delegates this activity to the IME subsystem to display an overlay window above the console host with suggestions. In an environment where overlay windows are not possible (like with certain remoting tools), the legacy console host may be required.

API Differences
The major known difference between legacy and current is the implementation of UTF-8. The legacy host has extremely rudimentary and often incorrect support of UTF-8 with code page 65001. The current console host contains incremental improvements release-over-release of Windows 10 to improve this support. Applications that are attempting to rely on predicting "known incorrect" interpretations of UTF-8 from the legacy console will find themselves receiving different answers as support is improved.

Other differences experienced with APIs should be reported to the microsoft/terminal GitHub repository or via the Feedback Hub for triage and possible remediation.
Top
#214272 - 2023-12-18 09:34 PM Re: VBSCRIPT end of the Road ahead. [Re: Allen]
NTDOC Administrator Offline
Administrator
*****

Registered: 2000-07-28
Posts: 11627
Loc: CA
Personally I've never used the Legacy Console and though I've read thousands and thousands of user logs I've not seen anyone using it either.

That doesn't mean that perhaps some API call is being made that is not shown in the logs but my guess is that it's for very old software which most people are not running something that old.
Top
#214273 - 2023-12-18 11:19 PM Re: VBSCRIPT end of the Road ahead. [Re: NTDOC]
Allen Administrator Offline
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4562
Loc: USA
I thought they were talking about CMD.exe. What other console is there?
Top
#214274 - 2024-01-11 03:29 AM Re: VBSCRIPT end of the Road ahead. [Re: Allen]
Sealeopard Offline
KiX Master
*****

Registered: 2001-04-25
Posts: 11165
Loc: Boston, MA, USA
Isn't PowerShell a console? i actually ended up writing a PowerShell script recently, took a while to get used to a different syntax.
_________________________
There are two types of vessels, submarines and targets.

Top
#214275 - 2024-01-11 04:05 AM Re: VBSCRIPT end of the Road ahead. [Re: Sealeopard]
Allen Administrator Offline
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4562
Loc: USA
Based on very limited googling, it appears that Legacy Mode is not something most people use. You can enable/disable by right clicking the title bar of CMD.exe or Powershell, select properties, and then check the box at the bottom of the page. I've never had a reason to use it.
Top
#214276 - 2024-01-12 03:14 AM Re: VBSCRIPT end of the Road ahead. [Re: Allen]
Glenn Barnas Administrator Offline
KiX Supporter
*****

Registered: 2003-01-28
Posts: 4401
Loc: New Jersey
Um, who are all these people?
Better question is where have they been all this time? \:\)

Hope everyone is doing great and knowing that our beloved scripting engine will keep working!
_________________________
Actually I am a Rocket Scientist! \:D

Top
#214277 - 2024-01-30 09:43 AM Re: VBSCRIPT end of the Road ahead. [Re: Sealeopard]
Arend_ Moderator Offline
MM club member
*****

Registered: 2005-01-17
Posts: 1896
Loc: Hilversum, The Netherlands
I've made the switch a few years ago, took some time to get used to it, but now I love it.
I've rewritten all my nice KiX Scripts, especially the GUI ones to powershell.
Leveraging everything .Net has to offer, I do stick to Powershell 5.* though, since that runs native on Windows 10/11.
Top
#214316 - 2025-09-10 10:43 PM Re: VBSCRIPT end of the Road ahead. [Re: Arend_]
Allen Administrator Offline
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4562
Loc: USA
https://www.neowin.net/news/vbscript-on-...y-vba-projects/

Since Microsoft was in the news again today reminding everyone that VBScript is being depreciated, I finally sat down and started trying to figure where I might feel this.

Inputbox(), WSHPipe(), and WSHShortCut() are the ones I immediately noticed.

Rarely, I need Inputbox, which was so slickly covered by scriptcontrol. After a ton of work (no thanks to Microsoft Copilot) here is a version using Powershell.


 Code:
Function InputBox($sPrompt, Optional $sTitle, Optional $sDefault)
    dim $PSCommand, $FH, $RC, $TempFile
    If Not $sTitle
      $sTitle = "Input Prompt"
    EndIf
    $TempFile = "%TEMP%\ps_inputbox.txt"
    if exist($TempFile)
      DEL $TempFile
    endif
    $PSCommand = 'powershell -Command "Add-Type -AssemblyName Microsoft.VisualBasic; '
    $PSCommand = $PSCommand + "$input = [Microsoft.VisualBasic.Interaction]::InputBox('" + $sPrompt + "','" + $sTitle + "','" + $sDefault + "'); "
    $PSCommand = $PSCommand + "$input | Out-File -FilePath '" + $TempFile + "' -Encoding ASCII"
    ;$PSCommand = "%COMSPEC% /c " + $PSCommand
    SHELL $PSCommand
    $fh = FreeFileHandle()
    If Open($fh, $TempFile) = 0
      $InputBox = ReadLine($fh)
      $RC=Close($fh)
    EndIf
EndFunction


Would someone mind checking this out and see if you can find issues with it and or report back if works for you?

I'm digging into details about the other two functions.
Top
#214317 - 2025-09-11 01:49 AM Re: VBSCRIPT end of the Road ahead. [Re: Allen]
Allen Administrator Offline
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4562
Loc: USA
I asked if using createobject("WScript.shell) would be affected by the vbscript depreciation. This is the response according to Microsoft Copilot....

"If you're using KiXtart or PowerShell to call COM objects, you're fine—until Microsoft decides to deprecate those COM interfaces too (which they haven’t announced yet"

 Quote:

what does safe for now mean?
“Safe for now” means that your current usage of CreateObject("WScript.Shell") in KiXtart or PowerShell is not directly impacted by VBScript’s deprecation—but it’s living on borrowed time.

Here's the nuance:
VBScript deprecation targets the vbscript.dll engine, which interprets .vbs files and embedded VBScript in HTAs and legacy apps2.

WScript.Shell is a COM object, not VBScript itself. You can still instantiate it from:

KiXtart

PowerShell

JScript

VB.NET

Even compiled C++ or C# via COM

So yes, CreateObject("WScript.Shell") is technically safe—but only outside of VBScript.

⚠️ What “safe for now” really means:
If you're using VBScript as the host language, like .vbs files or HTAs with <script language="VBScript">, those will eventually break.

If you're using KiXtart or PowerShell to call COM objects, you're fine—until Microsoft decides to deprecate those COM interfaces too (which they haven’t announced yet).
Top
#214318 - 2025-09-11 02:58 AM Re: VBSCRIPT end of the Road ahead. [Re: Allen]
Glenn Barnas Administrator Offline
KiX Supporter
*****

Registered: 2003-01-28
Posts: 4401
Loc: New Jersey
Personally, I have never used InputBox(), instead using KixForms. We deploy/register the DLL to be able to use Kix to run system-service type code via NSSM.exe. Since it's there, we leverage it for the one user-based interface app.

WshShortCut is used only in the install logic of our software - one call during the install and a second that runs daily to create the startup link if it's missing.

We do use WshPipe pretty extensively, with nearly 150 references across 36 of our applications. The team here has been looking at building an EXE or DLL that we could invoke that would replicate the ability to capture STDOUT/STDERR. We also have modified WSHPIPE pretty extensively to allow more control over returning either or both streams, control the wait time, and whether we terminate the app or not after the wait time expires.
_________________________
Actually I am a Rocket Scientist! \:D

Top
#214319 - 2025-09-11 03:18 AM Re: VBSCRIPT end of the Road ahead. [Re: Glenn Barnas]
Allen Administrator Offline
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4562
Loc: USA
Based on the response I got from CoPilot, it appears that wscript.shell scripts will be unaffected by the vbscript depreciation, so in theory WSHShell should be fine.
Top
#214320 - 2025-09-20 06:55 PM Re: VBSCRIPT end of the Road ahead. [Re: Allen]
ChristopheM Offline
Hey THIS is FUN
*****

Registered: 2002-05-13
Posts: 311
Loc: STRASBOURG, France
hello,
According to Microsoft Tech Community Blog ( VBScript deprecation: Timelines and next steps), cscript is deprecated but not yet completely dead.
Since Windows 11 24H2, cscript is an optional feature enabled by default. Around 2027, cscript will be optional disabled by default (but still available). And next (but date isn't defined now), cscript will be removed from Windows.
So there should be no impact in the near future for KIX scripts
_________________________
Christophe

Top
#214321 - 2025-09-21 02:58 AM Re: VBSCRIPT end of the Road ahead. [Re: ChristopheM]
Allen Administrator Offline
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4562
Loc: USA
@ChristopheM Exactly. Just trying to get the conversation going about this. It will be here quicker than we think.

I know there are scripts that we use that borrows from vbscript, especially the scriptcontrol object. So personally, I wanted to get everyone thinking about it, and if possible, post functions/code that effects you. Then maybe we can have a community to work around the problems.
Top
#214322 - 2025-09-21 03:23 PM Re: VBSCRIPT end of the Road ahead. [Re: Allen]
ChristopheM Offline
Hey THIS is FUN
*****

Registered: 2002-05-13
Posts: 311
Loc: STRASBOURG, France
Like glenn, we use our own version of InputBox, based on kixforms (version 2.47.6), which is deployed on each workstation and servers. Here is the code of the function :
 Code:
/*------------------------------------------------------------------------------
;function:
;  InputBox
;
;Author:
;  Christophe MELIN (christophe.melin68@outlook.fr)
;
;Action:
;  show a dialog box to get an input from a user
;
;Syntax:
;  InputBox( $strtitle, $strprompt, $strDefault, $PasswordChar )
;
;Parameters:
;  StrTitle   : REQUIRED. String value indicating the title of the window
;  StrPrompt  : REQUIRED. prompt before the input box
;  StrDefault : REQUIRED. default value in the input box
;
;  PasswordChar : OPTIONAL char to display if masked input
;
;returns:
;  string in the the inputbox if OK Button clicked empty string if Cancel buton clicked
;
;Dependencies:
;  KiXFormsv 2.47
;-----------------------------------------------------------------------------*/
Function InputBox( $strtitle, $strprompt, $strDefault, optional $PasswordChar )
  dim $, $strInput, $rc, $oldVars, $oldMacros

  $oldVars = SetOption( "NoVarsInStrings", "ON" )
  $oldMacros = SetOption( "NoMacrosInStrings", "ON" )

  dim $InputBoxForm
  $Inputboxform = CreateObject("Kixtart.Form")
  $Inputboxform.FontName      = "Tahoma"
  $Inputboxform.FontSize      = 10
  $Inputboxform.ClientHeight  = 250
  $Inputboxform.ClientWidth   = 400
  $Inputboxform.text          = $strtitle
  $Inputboxform.tag           = 1

  dim $lblInputboxPrompt
  $lblInputboxPrompt          = $Inputboxform.Label
  $lblInputboxPrompt.HEIGHT   = 19
  $lblInputboxPrompt.LEFT     = 10
  $lblInputboxPrompt.TOP      = 20
  $lblInputboxPrompt.WIDTH    = $Inputboxform.width - (2 * $lblInputboxPrompt.left)
  $lblInputboxPrompt.text     = $strprompt

  dim $txtInputboxPrompt
  $txtInputboxPrompt          = $Inputboxform.TextBox
  $txtInputboxPrompt.HEIGHT   = 25
  $txtInputboxPrompt.LEFT     = $lblInputboxPrompt.LEFT
  $txtInputboxPrompt.TOP      = $lblInputboxPrompt.bottom + 5
  $txtInputboxPrompt.Text     = $strDefault
  $txtInputboxPrompt.WIDTH    = $lblInputboxPrompt.width
  if $PasswordChar
    if Trim($PasswordChar)
      $txtInputboxPrompt.passwordchar = $PasswordChar
    endif
  endif


  dim $btnInputboxOK
  $btnInputboxOK              = $Inputboxform.button("OK")
  $btnInputboxOK.FONTNAME     = "Arial"
  $btnInputboxOK.FONTSIZE     = 10
  $btnInputboxOK.FONTBOLD     = 1
  $btnInputboxOK.WIDTH        = 80
  $btnInputboxOK.HEIGHT       = 19
  $btnInputboxOK.LEFT         = 10
  $btnInputboxOK.Top          = $txtInputboxPrompt.bottom + 10
  $btnInputboxOK.OnClick      = "$Inputboxform.hide() $Inputboxform.tag=0"
  $btnInputboxOK.Default      = 1

  dim $btnInputboxCancel
  $btnInputboxCancel          = $Inputboxform.button("Cancel")
  $btnInputboxCancel.FONTNAME = "Arial"
  $btnInputboxCancel.FONTSIZE = 10
  $btnInputboxCancel.FONTBOLD = 1
  $btnInputboxCancel.WIDTH    = 80
  $btnInputboxCancel.HEIGHT   = 19
  $btnInputboxCancel.LEFT     = $btnInputboxOK.left + $btnInputboxOK.width + 10
  $btnInputboxCancel.Top      = $btnInputboxOK.Top
  $btnInputboxCancel.OnClick  = '$Inputboxform.hide()  $txtInputboxPrompt.Text = ""'

  $btnInputboxCancel.Default  = 0
  $btnInputboxCancel.Cancel   = 1

  $Inputboxform.ClientHeight  = $btnInputboxOK.bottom + 10

  $Inputboxform.Center
  $=$Inputboxform.Show()
  $=$txtInputboxPrompt.SetFocus()
  while $Inputboxform.Visible
    $=Execute($Inputboxform.DoEvents)
  loop

  $strInput = $txtInputboxPrompt.Text
  $rc = $inputboxform.tag
  $Inputboxform = 0

  $inputbox = IIF( $rc, "", $strInput )

  $ = SetOption( "NoVarsInStrings", $oldVars )
  $ = SetOption( "NoMacrosInStrings", $oldMacros )
  exit $rc
endfunction

And following, a simple example of use of this function :
 Code:
$username = InputBox( "Get identity", "select user name", "%username%" )
if not @error
  $password = InputBox( "Get password", "password of "+$username, "", "*" )
  if not @error
    "username : " $username ?
    "password : " $password ?
  endif
endif

Is it post of functions / code like that you are waiting for ?

PS : If you want, you can reformat the code with syntax highlighting
_________________________
Christophe

Top
#214323 - 2025-09-30 05:55 PM Re: VBSCRIPT end of the Road ahead. [Re: ChristopheM]
Allen Administrator Offline
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4562
Loc: USA
Thank for posting your script. I'm sure someone will appreciate you sharing that.

I had hopes that korg community would come back around and not only share scripts that were going to break, but also, we could work on ways to fix the scripts, that might lead to some jewel like when we found scriptcontrol. Unfortunately, it looks like the korg community is basically a ghost town. I knew this, but somehow forgot. Anyway, my heart was in the right place. \:\)
Top
#214325 - 2025-10-26 07:10 AM Re: VBSCRIPT end of the Road ahead. [Re: Allen]
NTDOC Administrator Offline
Administrator
*****

Registered: 2000-07-28
Posts: 11627
Loc: CA
Not doing System Admin work anymore for many years now.

I do create PowerShell scripts for remote support and more and more moving towards Python scripts.
Top
#214326 - 2025-10-28 08:50 PM Re: VBSCRIPT end of the Road ahead. [Re: NTDOC]
BradV Offline
Seasoned Scripter
****

Registered: 2006-08-16
Posts: 687
Loc: Maryland, USA
I haven't done any Windows scripting for quite a while. My scripting is all done for RHEL 8 & 9. Just stop by occasionally to see what is going on? \:\)
Top
Page 1 of 1 1


Moderator:  Arend_, Allen, Jochen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Mart 
Hop to:
Shout Box

Who's Online
0 registered and 739 anonymous users online.
details
Newest Members
M_Moore, BeeEm, min_seow, Audio, Hoschi
17883 Registered Users
My Cookies · Mark all read Powered by UBB.threads™ Contact Us · KiXtart.org website · Top

Generated in 0.076 seconds in which 0.028 seconds were spent on a total of 13 queries. Zlib compression enabled.
Search the board with:
superb Board Search
or try with google:
Google
Web kixtart.org