Wiki editing discussion | MSX Resource Center (Page 69/194)

Enlighted (6429)

03-05-2020, 15:28

mars2000you wrote:

version 2.41 adds the environment variable TABORDER to the SET command

SET command can define any environment variable. Everyone can create a new variable using SET or DOS function. For example, EXPERT is not a simple variable. This is also a setting command that give a value in the variable of the same name. It is the same for some other commands like TIME for example. Any developers can also create new settings commands for its application that give a value in the variable (of the same name because that is the precept of DOS).

mars2000you wrote:

Sets or displays the MSX-DOS 2 environment variables.

SET allows us to define an environment variable and/or set parameters. It is not used to display variables except with a few setting commands.

By Dolphin101546015

Champion (336)

03-05-2020, 15:34

gdx wrote:

mars2000you wrote:

Sets or displays the MSX-DOS 2 environment variables.

SET allows us to define an environment variable and/or set parameters. It is not used to display variables except with a few setting commands.

Type: SET
without parameters

By gdx

Enlighted (6429)

03-05-2020, 15:43

The sentence is not clear because SET TIME displays the variable but this is not the case for many others.

By pgimeno

Champion (328)

03-05-2020, 19:56

It displays any variables for me (MSXDOS 2.20).

A:\>SET PATH
; A:\UTIL
A:\>SET WHATEVER=HELLO
A:\>SET WHATEVER
HELLO
A:\>SET NONEXISTENT
A:\>

Of course the display is blank if the variable is not set.

By gdx

Enlighted (6429)

05-05-2020, 10:13

It would be better to create a page for environment variables instead of putting that in the description of SET.

By tfh

Prophet (3424)

05-05-2020, 15:27

Regarding Undumped MSX Software list: New Adam & Eve is now available. Can it be updated, or are there any specific requirements before this is done (Checking, validating?)
Also, I did notice that in this wiki page there are some links to msxarchive to newly dumped titles (mainly Korean). I guess this is not allowed to due msx.org regulations?

By gdx

Enlighted (6429)

12-05-2020, 15:45

I suggest that we remove the square brackets to describe the commands/instructions syntax because it is sometimes difficult to respect all the possibilities without making it difficult to read. I think it's easier to put comments.

Here is an example with SCREEN:
https://www.msx.org/wiki/SCREEN

By mars2000you

Enlighted (6556)

15-05-2020, 14:23

Nyyrikki, take a look at this Wiki page; https://www.msx.org/wiki/VARPTR()

in 2018, you have contributed to this page by giving details about the working of the VARPTR instruction:

"Returns a pointer to either the beginning of FCB (File Control Block) associated with the specified file number or the actual memory address of the first byte of the variable passed. In case the variable is string the address of string pointer is returned. String pointer contains length & address of the string (3 bytes)."

Unfortunaly, GDX has recnntly destroyed that and replaced your text by this one:

"Returns the memory location of the FCB (File Control Block) of first/second file or the contain location of a variable in use."

I am not happy with this change, and I guess it's also your case.

Also the other MRC visitors can compare both texts and make their opinion.

By NYYRIKKI

Enlighted (6091)

15-05-2020, 15:08

mars2000you wrote:

Unfortunaly, GDX has recnntly destroyed that and replaced your text by this one:

"Returns the memory location of the FCB (File Control Block) of first/second file or the contain location of a variable in use."

I am not happy with this change, and I guess it's also your case.

Well... At least it is not correct as this is no way limited to only first/second file... The limitation comes from MAXFILES-command.

By gdx

Enlighted (6429)

15-05-2020, 15:24

OK, about the files this is not correct, but the rest is better than before.

Edit: I edit the explanation about the file. Is it better like that?