BrowserLauncher2 has problems on Windows 98. The third argument passed to command.com (zero length string) is not accepted. The following work on my test system (Windows 98 SE 4.10.2222 A with Internet Explorer 6) :
Previously I've made a one like hack to the original BrowserLauncher. It would be great if this could be corrected in BrowserLauncher2. I would suggest removing the class StandardCommandArgs from the DefaultWindowsBrowserLauncher base class and moving this code up the hierarchy via an abstract method like:
Hi All,
BrowserLauncher2 has problems on Windows 98. The third argument passed to command.com (zero length string) is not accepted. The following work on my test system (Windows 98 SE 4.10.2222 A with Internet Explorer 6) :
command.com /c start /max "http://www.papercut.biz/"
or
command.com /c start "http://www.papercut.biz/"
Previously I've made a one like hack to the original BrowserLauncher. It would be great if this could be corrected in BrowserLauncher2. I would suggest removing the class StandardCommandArgs from the DefaultWindowsBrowserLauncher base class and moving this code up the hierarchy via an abstract method like:
protected abstract String[] getStandardComandArgs()
Each platform subclass would implement it's own version and this inturn would avoid the need to pass through the command program via the constructor.
Happy to provide a patch if this would be of as stance.
Cheers,
Chris
Just to close off this thread - Jeff fixed this problem in RC4. Thanks Jeff!