Pleaseeee remove or disable if possible the commandline colors they're buggy! When I execute .bat files the path is altered so they always mess up. I wonder why people in this forum had only problems with visual studio: command line colors mess up most of the bat/nt scripts not only visual studio.

It is also a security issue:

for example I have a bat file with "del *.exe" in c:\myfolder\

if I run the bat file from explorer normally the path is c:\myfolder\ and all the exe files of myfolder are deleted.

if I run it from explorer and command line colors are enabled path is c:\windows\system32 guess what will happen? Screams everywhere! eek!

Please if possible turn it off in the installer or just remove it before somebody gets hurt !

Ok, I will try to figure out a solution for that before being forced to remove it from installer.

Hello, Xpero. Just wanted to add a few things : some reported bugs, like to small input boxes when selecting custom colors, were indeed Tahoma MS Shell Dlg issue, like you presumed. So not really an Xpize bug, I think... Second, I want to add PostgreSQL to applications which have problems with command line colors tweak - Windows installation of PostgreSQL will fail if command line tweak is enabled.

Thanks for the special gift and all the great stuff Wish you merry Xmas and happy hollidays.

Edited December 25, 200520 yr by Bagsnak

Thanks for reporting. Merry Xmas to you too

PLEASE REMOVE IT!

The most people dont use CMD and the most people that using it dont care or have problems with it. So XPize 4.2 Beta 3 or final without it?

Edited December 25, 200520 yr by laurens

even i feel that we can do away with it. I think 90% or even more than that cmds use comes in automated scripts and processes. so better we leave it out.

I will

and again 1 click less for installing XPize

Solution reposted as a new topic. See

http://www.msfn.org/board/index.php?act=ST...t=0#entry441887

Edited December 30, 200520 yr by ronin2040

Installation of PostgreSQL on WinXP SP2 still fails after changing autorun entry for command prompt ... With defaults it's ok ...