Jump to content











Photo
- - - - -

System,HasDOS8_3 command


  • Please log in to reply
7 replies to this topic

#1 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 10 May 2011 - 04:50 PM

Hi all,

i found in the history file of WB

System,HasDOS8_3 command

and i can not figure out what it is good for?

Can anyone explain please, thanks !

#2 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 10 May 2011 - 05:00 PM

A glitch!

Written in history, added to magic wand, but not implemented!

Peter

#3 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 10 May 2011 - 08:30 PM

OK, so will it be added and what exactly will this do?

#4 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 10 May 2011 - 08:39 PM

OK, so will it be added and what exactly will this do?

No opinion. All Win based systems have the 8_3 ability. Maybe there is an idea to check for *ix OS's abilities. But currently I do not see any propability to add. I suggest: Just forget the question.

Peter

#5 paraglider

paraglider

    Gold Member

  • .script developer
  • 1729 posts
  • Location:NC,USA
  •  
    United States

Posted 11 May 2011 - 12:02 AM

Although windows has an 8.3 file name option it can be disabled via the registry. Its usually not a good idea though has some programs depend on it. Look in:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
NtfsDisable8dot3NameCreation

#6 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 11 May 2011 - 05:38 AM

OK, thank for the info...

Disabeling 8.3 support should be a rather rare case, so i believe we do not need this function...

#7 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10547 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 11 May 2011 - 07:57 AM

Yes, this function should not be provided by winbuilder. In such case, it is best for the script developer to implement it himself.

It would be nice to have winbuilder as much independent from windows as possible, so that one day it can run more comfortably in other OS platforms.

#8 sbaeder

sbaeder

    Gold Member

  • .script developer
  • 1338 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 11 May 2011 - 04:14 PM

Well, I tend to disable it - mostly for speed reasons. Making NTFS go back and also create a second 8.3 file name entry is a bit "archaic" - YES, there may be some really old programs that you want to use that can't handle the long file names (or spaces in file names), but for me, I have upgraded (or chosen different tools) long ago.

Main thing is that for a PE, there isn't any real reason to disable it - but agree that I don't see any need to implement a check for it inside WB either.

BUT, this does raise the issue of do we have a complete / correct set of docs for all the things added? If not, what commands do we need to document (and do we need folks to help write the docs)?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users