Emuforums.com - View Single Post

**drkIIRaziel** · April 2nd, 2007

As the release was realy tiring to make , there are a few things that are included in it , but not documented.Please note that these are 'not supported features' and may get removed/replaced in feature versions or even not work at all

.Try em on your own risk ...

nullDC.cfg file :
There are varius settings that are not exposed in the interface.That includes AntiAlias & resolution settings for the pvr plugins.To restore default settings , just delete the config file

.

Command line params (These are mostly usefull to developers):

-nosse2 , -nosse3 , -nossse3
These disable the use of some instruction sets (sse2/3/S3).(Not realy usefull)

-serial "file here"
Redirects the serial output to the given file.It can also redirect it to a COM port (-serial \\.\COM1).The file MUST exist before loading nullDC.

-slave <pipe1 handle> <pipe2 handle>
Writes serial output to pipe1 , reads from pipe2.The handles have to be created properly first (ie : -slave 912 913).It can be used to redirect the serial IO to another application

.gdi files:

The ImageReader plugin supports a format to load gdrom dumps.
here's the structure :
Entry Count
Track StartSector ctrl SectorSize File Offset
....
Track : track number
StartSector : start sector on the gdrom to map the file
ctrl : 4 -> data , 0 -> audio
SectorSize :Sector size for the data in the file , 2048 , 2352 & a few others are supported.If this is set to 0 the file is considered 'missing'
File : file to read the data from
Offset : byte offset into file to read the data from. Can be both negative and positive

The first 2 entrys are for the low density area (tracks 1 & 2,session 1)
The rest of em are on the hi density area (tracks 3+ , session 2)

Here are a few examples :

Tony Hawks Pro Skater 1:

Code:

5
1 0 0 0 none 0
2 0 0 0 none 0
3 45000 4 2352 45000to63139.bin -8
4 63288 0 0 none 0
5 69313 4 2352 69313to549150.bin -8

the 1,2 and 4 tracks are missing from my dump , the -8 is to offset the files a bit (dumped using cdrwin so the format is a bit different)

Visual Park

Code:

13
1 0 0 0 none 0
2 0 0 0 none 0
3 45000 4 2048 track3.iso 0
4 445516 0 0 track04.raw 0
5 449104 0 0 track05.raw 0
6 453213 0 0 track06.raw 0
7 455855 0 0 track07.raw 0
8 469617 0 0 track08.raw 0
9 483437 0 0 track09.raw 0
10 486080 0 0 track10.raw 0
11 491965 0 0 track11.raw 0
12 543479 0 0 track12.raw 0
13 547889 4 2048 track13.iso 0

tracks 1,2,4,5,6,7,8,9,10,11,12 are missing here (audio tracks -- they just get replaced by silence)

Thats it , i hope that helps.

April 2nd, 2007	#1 (permalink)
drkIIRaziel Emu author Join Date: Jan 2006 Location: Athens,Greece Posts: 580	'Undocumented' nullDC features As the release was realy tiring to make , there are a few things that are included in it , but not documented.Please note that these are 'not supported features' and may get removed/replaced in feature versions or even not work at all .Try em on your own risk ... nullDC.cfg file : There are varius settings that are not exposed in the interface.That includes AntiAlias & resolution settings for the pvr plugins.To restore default settings , just delete the config file . Command line params (These are mostly usefull to developers): -nosse2 , -nosse3 , -nossse3 These disable the use of some instruction sets (sse2/3/S3).(Not realy usefull) -serial "file here" Redirects the serial output to the given file.It can also redirect it to a COM port (-serial \\.\COM1).The file MUST exist before loading nullDC. -slave <pipe1 handle> <pipe2 handle> Writes serial output to pipe1 , reads from pipe2.The handles have to be created properly first (ie : -slave 912 913).It can be used to redirect the serial IO to another application .gdi files: The ImageReader plugin supports a format to load gdrom dumps. here's the structure : Entry Count Track StartSector ctrl SectorSize File Offset .... Track : track number StartSector : start sector on the gdrom to map the file ctrl : 4 -> data , 0 -> audio SectorSize :Sector size for the data in the file , 2048 , 2352 & a few others are supported.If this is set to 0 the file is considered 'missing' File : file to read the data from Offset : byte offset into file to read the data from. Can be both negative and positive The first 2 entrys are for the low density area (tracks 1 & 2,session 1) The rest of em are on the hi density area (tracks 3+ , session 2) Here are a few examples : Tony Hawks Pro Skater 1: Code: 5 1 0 0 0 none 0 2 0 0 0 none 0 3 45000 4 2352 45000to63139.bin -8 4 63288 0 0 none 0 5 69313 4 2352 69313to549150.bin -8 the 1,2 and 4 tracks are missing from my dump , the -8 is to offset the files a bit (dumped using cdrwin so the format is a bit different) Visual Park Code: 13 1 0 0 0 none 0 2 0 0 0 none 0 3 45000 4 2048 track3.iso 0 4 445516 0 0 track04.raw 0 5 449104 0 0 track05.raw 0 6 453213 0 0 track06.raw 0 7 455855 0 0 track07.raw 0 8 469617 0 0 track08.raw 0 9 483437 0 0 track09.raw 0 10 486080 0 0 track10.raw 0 11 491965 0 0 track11.raw 0 12 543479 0 0 track12.raw 0 13 547889 4 2048 track13.iso 0 tracks 1,2,4,5,6,7,8,9,10,11,12 are missing here (audio tracks -- they just get replaced by silence) Thats it , i hope that helps.