PgcEdit 0.6.3.1

[r0lZ]

Because there are no subpics defined in the IFOs for them!

[CoNS]

:o Ok I got it! Sorry about that!

I was so focused on the fact that it was the first of the VTS with missing VOBs that displayed differently. Maybe because it (coincidently?) was the same pattern last time I edited a disc with all VOBs missing except the main movie VOBs. Or maybe because I thought the logical process would be to first check for VOBs and then look for subpics in the IFO...

[BOB66]

Hi :)

I`ve got a problem with PgcEdit 0.6.2 when I want to burn a DVD. It stops (close the PgcEdit-Window) without any (error)message after I push "OK" in "DVD Burn" Menu. No File is created in the targetdir. No difference when I only want to make a ISO on HDD, without burning. One (Testing...) maybe two messages in the statusbar bevor, but to fast for reading this. No "ISO creation log" is shown. Split to 1GB chunks is activated.

Burning a DVD with ImgToolClassic 0.91.6 and ImgBurn 1.1.0.0 works well. Also Nero 6 with ImgTool Burn.
No foreign characters in the directory names of the install path of PgcEdit, ImgTool Classic and ImgBurn. Daemon Tools are not installed (no path).

Windows ME
AMD Athlon XP 2400
BENQ 1640

Any Ideas?

BOB66

[r0lZ]

No idea.

Are you sure the path to mkisofs is correct? Which version of mkisofs are you using? (You can examine it in the burn setup dialog)

Could you send me your configuration files? I need burn.cfg and pgcedit.cfg, both in "C:\Documents and Settings\<your user name>\Application Data\PgcEdit\". Send them to pgcedit at tiscali dot be.

You could also try the new version of ImgTool Classic.

[BOB66]

No idea.

Are you sure the path to mkisofs is correct? Which version of mkisofs are you using? (You can examine it in the burn setup dialog)

Could you send me your configuration files? I need burn.cfg and pgcedit.cfg, both in "C:\Documents and Settings\<your user name>\Application Data\PgcEdit\". Send them to pgcedit at tiscali dot be.

You could also try the new version of ImgTool Classic.

Thank`s for your fast replay :)

The version of mkisofs is 2.01, I can see it in the burn setup dialog.
Then I installed the new ImgTool Classic 0.91.7, but it is still the same problem.

So the needed files are on the way to you ;)

See you
BOB66

[r0lZ]

Well, I am currently generating an ISO with the same parameters as you, and I have no problems.
Could you do another thing? When the ISO is created, a batch file is created in the TEMP folder, and this batch is used to call mkisofs. Could you open a dos prompt, and type:
cd %TEMP%
MakeISO > makeiso.log
start %TEMP%

The last command will open your TEMP folder. Locate MakeISO.bat and makeiso.log, and send me the files, or copy the content of the files and paste it here. (If there are many lines in the log starting with "x.x% done, estimate finish ..." you can delete them. I don't need them.)

[_Nihil_]

(Ignore this post if i'm too stupid to find existing feature / functionality)

1. Add title on existing pgc / vtst
2. Remove any logical pgc / vtst

Example: I will create new DVD and Impost VTST Title. Imported VTST doesn't have title so to get title i either have to use Clone PGC or New "play all" Title. So in the end i have DVD with VMG & VTST 1,1 & VTST 1,2. VTSTs are identical except that 1,1 doesn't have title.

Used PgcEdit versions 0.6.2 & 0.6.0

Yours: Nihil

[BOB66]

I get this message after the second line:

C:\WINDOWS>cd %TEMP%

C:\WINDOWS\TEMP>MakeISO > makeiso.log
/cygdrive/e/WIN_ME/IMGTOOL/IMGTOO~3/MKISOFS: No such host or network path. Cannot open '//.mkisofsrc'.
/cygdrive/e/WIN_ME/IMGTOOL/IMGTOO~3/MKISOFS: No such file or directory. Invalid
node - 2
****** ERROR returned by mkisofs! ******
C:\WINDOWS\TEMP>

makeiso.log: (is empty)

MakeISO.bat:

@echo off
"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no-pad -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -m *backup* -m *Backup* -m .DS_Store -m "Copy of *" -split-output "F:\SAHARA" 2>&1
if errorlevel 1 echo ****** ERROR returned by mkisofs! ******



BOB66

[r0lZ]

Hummm... Seems mkisofs is not correctly installed, or it's a bug in cygwin1.dll. I will have a look at the mkisofs doc to see if it is possible to disable the .mkisofsrc resource file. But don't expect a fix.

Maybe the problem is caused by an incompatibility with Windows ME/9X? (Mkisofs is a Linux program, compiled for Windows, and running under cygwin, something like a small emulator.) Anyway, fortunately, Microsoft has now discontinued his crappy Win 9X serie. You should consider upgrading to Windows XP. I guess the problem will disapear. And, as a bonus, you will be able to write files larger than 1GB!

[jeanl]

And, as a bonus, you will be able to write files larger than 1GB!
Imagine that! :scared:

[BOB66]

Hummm... Seems mkisofs is not correctly installed, or it's a bug in cygwin1.dll. I will have a look at the mkisofs doc to see if it is possible to disable the .mkisofsrc resource file. But don't expect a fix.

Maybe the problem is caused by an incompatibility with Windows ME/9X? (Mkisofs is a Linux program, compiled for Windows, and running under cygwin, something like a small emulator.) Anyway, fortunately, Microsoft has now discontinued his crappy Win 9X serie. You should consider upgrading to Windows XP. I guess the problem will disapear. And, as a bonus, you will be able to write files larger than 1GB!

But remember: I can make a ISO with ImgTool Classic, I guess it use also mkisofs. I`ve tested it a few minutes ago, now with the new version 0.91.7, it works well.

May be your right to have a look to Windows XP.... but ...

However:thanks:
Sleep a night and I`m sure when you get up tomorrow and you see yourself in the bathmirror - the idea for a fix is like a flash in you minds.;)


jeanl:
Windows ME with the file system FAT32 can not work with files bigger than 1Gb.
For Windows XP it`s no problem with file system NTFS. So you don`t need to split the Image File. It look`s much better and is easier to handle.

[bigotti5]

@r0lZ

In PgcEdit6.3beta5 "Close & Break trace" does not work for me (does not break the trace).
In 6.2, 6.3beta4 it works.

[r0lZ]

Right. Thanks for the info!

[r0lZ]

@BOB66

OK, let's try another thing.

Could you launch manually the mkisofs command in a DOS prompt, removing one argument at a time, until it works?

The original command is:
"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no-pad -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -m *backup* -m *Backup* -m .DS_Store -m "Copy of *" -split-output "F:\SAHARA" 2>&1

You should try those commands:
"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -m *backup* -m *Backup* -m .DS_Store -m "Copy of *" -split-output "F:\SAHARA" 2>&1

"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no-pad -V "SAHARA" -o "d:\SAHARA.ISO" -m *backup* -m *Backup* -m .DS_Store -m "Copy of *" -split-output "F:\SAHARA" 2>&1

"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no-pad -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -m *Backup* -m .DS_Store -m "Copy of *" -split-output "F:\SAHARA" 2>&1

"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no-pad -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -m *backup* -m .DS_Store -m "Copy of *" -split-output "F:\SAHARA" 2>&1

"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no-pad -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -m *backup* -m *Backup* -m "Copy of *" -split-output "F:\SAHARA" 2>&1

"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no-pad -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -m *backup* -m *Backup* -m .DS_Store -split-output "F:\SAHARA" 2>&1

"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no-pad -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -split-output "F:\SAHARA" 2>&1

"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no-pad -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -m *backup* -m *Backup* -m .DS_Store -m "Copy of *" -split-output "F:\SAHARA"

"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -V "SAHARA" -o "d:\SAHARA.ISO" -split-output "F:\SAHARA"

And report which command works well (if any!)
Don't try to burn the output ISO files!
Thanks.

[BOB66]

Interesting news!

the last one works!

all other not, because all the commands were cut after the 127`th letter

for example the original command:
C:\>"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no-pad -V "SAHARA
" -o "d:\SAHARA.ISO" -p PgcEdit -m *backup* -m *Bac
First I worked with copy/paste, but then with keyboard, the same limitation.

then the message from mkisofs:
/cygdrive/e/WIN_ME/IMGTOOL/IMGTOO~3/MKISOFS: No such host or network path. Canno
t open '//.mkisofsrc'.
/cygdrive/e/WIN_ME/IMGTOOL/IMGTOO~3/MKISOFS: Missing pathspec.
Usage: mkisofs [options] file...

Use mkisofs -help
to get a list of valid options.


BOB66 :)

[r0lZ]

Damn, it's not what I want!
It should be possible to execute a long command line from a batch file. Can you copy the same commands in a .bat file, and execute it? Should work.

BTW, it's another crazy limitation of Win 9X! 127 characters in a command line is somewhat limited. (Max 259 characters under XP, and about 2000 under Linux!)

[Drinken]

You can increase the limit by editing config.sys
Here's how. http://support.microsoft.com/kb/121059/en-us

[r0lZ]

Thanks, Drinken. Great tip. Do you know if the same limitation apply to batch files?

Anyway, it will probably not solve the issue of the PgcEdit burn, because, IMO, I cannot change a system file myself, w/o the explicit user content.

Why are the guys at M$ so stupid?! :eek:

[Drinken]

I think there's a limit for batch files, yes... I'll see if I can find any info.

Well, I'm not sure if this'll work, but it's worth a try. Try launching mkisofs via command /u:250 /C "mkisofs.exe Arg1 Arg2 ..."?

Dr.

[r0lZ]

Well, I can't do that, because of another limitation in Windows! :devil:
I need to launch mkisofs from a batch file, because otherwise I can't retrieve the stderr output.
But I suppose that I can launch the batch file the same way: command /u:250 /C MakeISO.bat
Byt it's more complicated than what I do now. I have to test if PgcEdit is running under Win9X and use command.com in this case, or the somewhat more powerful cmd.exe otherwise.

Sorry to ask such newbie questions, but I don't have a Win9X system to test.

[Drinken]

Yeah... AFAIK 250 is the max.
I just tried under XP:

command /u:250 /C C:\PROGRA~1\IMGtools\mkisofs.exe -dvd-video -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -m *backup* -m *Backup* -m .DS_Store -m "Copy of *" -split-output "F:\SAHARA" 2>&1
Didn't work, "The system cannot execute the specified program."
I don't have a 9x machine here so unable to test if it would behave the same way under 9x.
Same line with cmd works properly...

I would guess the easiest would be to pop up a window with instructions on how to edit config.sys to enable the workaround?

[ron spencer]

thanks

[r0lZ]

Drinken, I tried also command /u:250 under XP, without success. But the /u option is not listed in the output of command.com /?
Is it an option available only under 9X? If so, it's even mode crazy than I though!

[r0lZ]

Well, I have found a way to use long command lines in MS-DOS. The trick is to split the command in several parts which are placed in environment variables. Then, the command is generated using the variables rather than the full text. It works well in CMD.EXE, and in the XP version of COMMAND.COM, but I'm not sure it will work under Win ME.

BOB66, could you try it?
Copy the following MS-DOS script in a batch file (with a ".bat" extension), and execute it. Mkisofs should work.
(Note that I have used for this example the arguments you gave in a previous post. Of course, the DVD folder should still be present on your hard disc!)


set p="E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe"
set a1=-dvd-video -no-pad -p PgcEdit
set a2=-m *backup* -m *Backup* -m .DS_Store -m "Copy of *"
set a3=-split-output
set a4=-V "SAHARA"
set a5=-o "d:\SAHARA.ISO"
set a6="F:\SAHARA"
%p% %a1% %a2% %a3% %a4% %a5% %a6% 2>&1
pause

[Drinken]

Clever! I would never had thought about doing it that way. :)

[jeanl]

Clever! I would never had thought about doing it that way. :)
the things M$ stupidity will force you to do!
:D
jeanl

[BOB66]

Damn, it's not what I want!
It should be possible to execute a long command line from a batch file. Can you copy the same commands in a .bat file, and execute it? Should work.

BTW, it's another crazy limitation of Win 9X! 127 characters in a command line is somewhat limited. (Max 259 characters under XP, and about 2000 under Linux!)


OK,
I checked all lines it in a BAT file and this one (and the last) made an ISO:

"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no-pad -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -m *backup* -m *Backup* -m .DS_Store -m "Copy of *" -split-output "F:\SAHARA"

It`s nearly the original command without the "2>&1" at the end.

C:\WINDOWS\Desktop>"E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe" -dvd-video -no
-pad -V "SAHARA" -o "d:\SAHARA.ISO" -p PgcEdit -m *backup* -m *Backup* -m .DS_St
ore -m "Copy of *" -split-output "F:\SAHARA"
/cygdrive/e/WIN_ME/IMGTOOL/IMGTOO~3/MKISOFS: No such host or network path. Canno
t open '//.mkisofsrc'.
0.23% done, estimate finish Sat Jan 14 20:04:33 2006
......
99.87% done, estimate finish Sat Jan 14 20:02:09 2006
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 4248
Path table size(bytes): 42
Max brk space used 5000
2172731 extents written (4243 MB)

Results for me:
- there is no limitation to 127 characters with batch file
- it looks like that the "2>&1" at the end makes trouble

BOB66

[BOB66]

Well, I have found a way to use long command lines in MS-DOS. The trick is to split the command in several parts which are placed in environment variables. Then, the command is generated using the variables rather than the full text. It works well in CMD.EXE, and in the XP version of COMMAND.COM, but I'm not sure it will work under Win ME.

BOB66, could you try it?
Copy the following MS-DOS script in a batch file (with a ".bat" extension), and execute it. Mkisofs should work.
(Note that I have used for this example the arguments you gave in a previous post. Of course, the DVD folder should still be present on your hard disc!)


set p="E:\WIN_ME\ImgTool\ImgToolClassic\mkisofs.exe"
set a1=-dvd-video -no-pad -p PgcEdit
set a2=-m *backup* -m *Backup* -m .DS_Store -m "Copy of *"
set a3=-split-output
set a4=-V "SAHARA"
set a5=-o "d:\SAHARA.ISO"
set a6="F:\SAHARA"
%p% %a1% %a2% %a3% %a4% %a5% %a6% 2>&1
pause


I sended the result by email to you, did not work.

BUT IT WORKS without "2>&1" AND calling the batch file over DOS-prompt.

If I start the batch file direct, then it shows after the 5t line "no enough memory in the environment"

BOB66

[r0lZ]

If I start the batch file direct, then it shows after the 5t line "no enough memory in the environment"Aaaargh! It is definitively impossible to do anything with Win ME! No stderr redirection, no variable substitution! And what else?!

Solution: switch to XP, or, better, to Linux!
I can't help more. Ask Bill Gates why!

[Drinken]

Modify the Environment for a Specific MS-DOS Program
To increase the default environment space for a specific MS-DOS program, follow these steps: 1. Right-click the MS-DOS program icon, and then click Properties.
2. Click the Memory tab.
3. In the Initial Environment box, type the number of kilobytes (KB) that the program requires, and then click OK.

NOTE: The maximum amount of memory that you can allocate for an MS-DOS program is 4096 KB.

edit1:
Or: Edit config.sys again, and set SHELL=C:\COMMAND.COM /E:4096 /U:250 /P

I think the /U parameter is only available when using shell= in config.sys actually. There are lots of undocumented switches for MS software...

To be honest, I don't see a problem with editing config.sys as long as you make a backup.
This enviroment problem is easy enough to solve though. :)

Edit2:
I can't remember there being a problem with redirection in 9x, I'll look into it.

Edit3:

I forgot that ME ignores settings for the enviroment size in config.sys! The default space for environment variables is only 256 bytes!

To fix this:
1. Right-click the MS-DOS Prompt shortcut, and then click Properties.
2. Click the Memory tab.
3. In the Initial Environment box, set the initial environment size you want (from 256 to 4,096 bytes, in 256-byte increments).
4. Click OK.

[r0lZ]

Well, I have surfed the net, and found at several places that it is not possible to redirect stderr under Win 9X! I need that absolutely for the burn DVD function.
The line too long problem is also important, but w/o the redirection, I can't support Win9X anyway!

My last hope is that there is no real stderr stream under 9X, and that it is redirected anyway to stdout. In this case, the 2>&1 (which cause a syntax error) can be omitted, and everything is fine.
If it works, I will come back to the line too long and memory problems. But if it doesn't work, I will simply display a "Burn function not supported under Win 9X" dialog. Since win ME is outdated, I don't want to spend too many time trying to support it.

Thanks anyway for your help, Drinken.

[BOB66]

Well, I have surfed the net, and found at several places that it is not possible to redirect stderr under Win 9X! I need that absolutely for the burn DVD function.
The line too long problem is also important, but w/o the redirection, I can't support Win9X anyway!

My last hope is that there is no real stderr stream under 9X, and that it is redirected anyway to stdout. In this case, the 2>&1 (which cause a syntax error) can be omitted, and everything is fine.
If it works, I will come back to the line too long and memory problems. But if it doesn't work, I will simply display a "Burn function not supported under Win 9X" dialog. Since win ME is outdated, I don't want to spend too many time trying to support it.

Thanks anyway for your help, Drinken.


@r0lZ, @Drinken

thank`s for your help!:thanks:
But it looks like that`s not (so easy) to fix this for Windows ME. Don`t spend much more time for this.

PgcEdit is a very great and powerful tool !!!
It works without any (other) problems for me and I can burn with ImgToolClassic till I switch to XP.

BOB66:)

[r0lZ]

That's right. Thanks for your comprehension.

But take in mind that you cannot burn a DL media with ImgTool Classic, because it has no provision to select the layer break cell.

Anyway, when I'll have some free time, I will send you a little tcl script to see it the 2>&1 syntax can be safely omitted under WinME.

[blutach]

Another burn bug - is this known and solved?

Using v0.6.2 - Click on burn and it tells me the files need to be in VIDEO_TS. Click on OK. Moves them there but gives continual error about not being able to move Pgcedit_backup (when it has in fact been moved). Only way out of this is to cancel, after which main ISO image dialogue box comes up. Is this solved in a 0.6.3 beta 5?

EDIT: Also, is anyone experiencing problems with removing the Layer Break by unchecking the LB box? I had to manually make it "9" from "1" (there were no real angles) as unchecking it and OK did not "take".

Regards

[r0lZ]

Using v0.6.2 - Click on burn and it tells me the files need to be in VIDEO_TS. Click on OK. Moves them there but gives continual error about not being able to move Pgcedit_backup (when it has in fact been moved). Only way out of this is to cancel, after which main ISO image dialogue box comes up. Is this solved in a 0.6.3 beta 5?Yes, this bug is solved in the latest beta.

EDIT: Also, is anyone experiencing problems with removing the Layer Break by unchecking the LB box? I had to manually make it "9" from "1" (there were no real angles) as unchecking it and OK did not "take".Right. And this bug is still not fixed. Currently, the Layer Break checkbox is useless. You have to use the little Cell Flags dialog to change the seamless flag.
I will fix the problem right now.

[blutach]

Merci beaucoup. I'm just lazy I think - have installed 6.3.B5 and read the version history and figured this was the fix.

Wonder why the LB thingy got broken?

Regards

[r0lZ]

It's mainly because of the change in the interface. The communication between the checkbox and the cell flags button was broken.

[Drinken]

I think this has been reported earlier, but it's worth mentioning again I think.
PGCedits backup folders gets deleted correctly now when creating the ISO, but Vobblankers backup folder (in root) are left alone and gets included in the ISO.

Dr.

Edit: This is with beta5.

[r0lZ]

I can't reproduce this problem! Could you give me the exact filename (with the path) to your VB backup folder? And is it something special in the mkisofs log?

[Drinken]

No error in the log, just the default vobblanker_backup in the c:\Movie folder, not in c:\Movie\VIDEO_TS.

Name of VB Backup folder from memory, sorry I'm unable to check right now. I'll check later tonight if needed.

Edit: The only thing giving away that it's happening is if PGCedit decides to pad the ifos in the backup folder. Then the log shows pad of 2 ifos with the same name. I'll run a test now and post more specifics.

Edit2: Sorry about the delay, the name of the VB Backup folder is c:\Movie\VobBlanker_backup.

[Drinken]

Ok, so the layout is as follows...
Source: C:\MULAN\VIDEO_TS
VB backup folder located in C:\MULAN\VobBlanker_backup

Log output:
mkisofs log for DVD "MULAN"
From: "C:\Burn\MULAN"
DVD-TEXT General Name: ""
Provider ID: "MULAN"
Number of VTS: 12
Output file: "D:\Burn\MULAN.ISO"
Volume label: "MULAN"

mkisofs 2.01 X (i686-pc-cygwin)
The pad was 16 for file VIDEO_TS.IFO
The pad was 6 for file VTS_02_1.VOB
The pad was 6 for file VTS_12_1.VOB
The pad was 16 for file VIDEO_TS.IFO
The pad was 6 for file VTS_02_1.VOB
The pad was 6 for file VTS_12_1.VOB
Notice the duplicates, and lack of warnings/errors. I'm going to try putting the backupfolder inside VIDEO_TS now, see if it makes any difference.

Edit: After moving VobBlanker_backup into VIDEO_TS PGCedit prompts with the mkisofs Invalid node - -m error, and prompted if it should delete the backups and continue (YES), continue w/o deleting the backups (NO), or cancel.
There's a typo in the dialogue BTW, "mkisofs returnde the...". :)

So I guess the solution is to configure VB to store the backup folder inside VIDEO_TS.

[r0lZ]

Well, I have just modified (again) the way the burn function sends the mkisofs command. I hope now that this irritating - -m bug will be fixed. With some luck, the location of the backup will not matter any more.
A new beta will be available in a couple of days...

[blutach]

I've hated the --m bug since I first came across it. It's a plague and a pox!

Regards

[Denis Fomin]

First of all I would like to say thank you r0lZ for this unbelievable tool :) It's more than a knife it's an axe. I can literally butcher a DVD with it :) Carve it anyway I like it :)
And to the point. It's seems to be a bug in <Remap Titlesets> command in PgcEdit 0.6.2. The setup:

VMGM: has a button referencing VTS2 menu with the command
Jump to VTSM 2, Root menu (TTN 1)

VTS 2: here is the main feature and a menu

so as you can see this DVD's (R2 Taxi Driver btw) menu spans across VMG and VTS2. I want to make VTS2 into VTS1 so the main feature is in the first TitleSet and I'll be able to delete the rest of the TitleSets which are all kinds of extra material. I use PgcEdit's <Remap Titlesets> command. It does the file renaming alright but command
Jump to VTSM 2, Root menu (TTN 1)
in VMG does NOT change to
Jump to VTSM 1, Root menu (TTN 1)
as it should.
I changed it manually but thought you would like to know :) Plus it gave me the opportunity to say my thanks for PgcEdit :)

[r0lZ]

Thanks, Denis!
There was indeed a big bug in the remap titlesets function: the JumpSS commands in the menu buttons of the VMGM were modified, but not saved! Since the DVD is reloaded automatically after the remap titleset operation, the modified commands were overwritten by the original ones.
It's fixed now. Thanks again!

V0.6.3 will be released very soon. Probably today.

[r0lZ]

PgcEdit v0.6.3 release history:
A. It is now possible to bypass a menu with buttons with Kill Playback. The user is prompted to select the button to simulate.
A. Pgc EDitor -> Create new blank cell: New interface. It is now possible to insert the cell at the beginning of the PGC.
E. Pgc Editor -> Create New Blank Cell: The GUI has been revamped completely. It is now possible to use an existing and referenced Cell from the original VOB file, or, as before, to create a new blank cell. The button to call this function has been renamed from "Create a new blank cell" to "Create a new cell".
A. Pgc EDitor -> Create new blank cell and Reassign VOB/Cell ID: Option added to reuse the last tiny blank cell at the end of the VOB file (available only when that cell has been created previously by PgcEdit.)
E. Pgc Editor -> Create new blank cell and Reassign VOB/Cell ID: There is now a Preview button in the GUI to show the selected replace cell.
E. Jump to PGC upon DVD insert: When the target PGC is in a menu domain, the last title played before the target PGC is now always called (but not played) just before the target menu PGC so that a valid resume point exists when the menu is reached for the first time. This method should fix the (rare) problem caused by the usage of a RSM command in the menu to call the main title. Previously, the title PGC was called before the menu only when it was in the same titleset than the target menu.
E. When importing titles in a DVD with parental managment, the user is now prompted to remove the parental managment of the original DVD, and when importing a menu, it is prompted to clear the parental managment IDs of the menu PGCs, if there are IDs in the menu.
E. Burn DVD: Interface revamped, and new option to close automatically PgcEdit after a successful ISO creation.
E. Burn DVD: The new ImgBurn 1.1 command lines options /CLOSESUCCESS and /WAITFORMEDIA are now used instead of /CLOSE (though /CLOSE is still used if the ISO image is burnt with DVD Decrypter.) Please note that you need ImgBurn 1.1.0.0 or the "Close ImgBurn" option will not work!
F Burn DVD: The layer break sector passed to ImgBurn or DVDD was wrong when burning a DL DVD-R. (No problem with DL DVD+R.)
F. Burn DVD: Changed the way the backup files are excluded from the compilation. In v0.6.2, the old method caused harmless errors when the DVD files were moved in the new VIDEO_TS directory.
F? Burn DVD: Changed again the syntax to exclude the backup files from the compilation to avoid the mkisofs "-m" bug.
F Burn DVD: A batch file is now always used under Windows to call mkisofs, and the mkisofs command line is split in environment variables to avoid the line too long M$-DOS bug under Win9X.
F? Burn DVD: Redirecting stderr to stdout doesn't work under Win9X! Workaround: the output of mkisofs is not well checked under Win9X. For this reason, the user should take care of the error messages in the log!
See the warning under Win9X when the Burn Setup dialog is opened.
F. Burn DVD: Wrong error message when moving the backup folders in VIDEO_TS.
F. Burn DVD: Under Windows, it is now impossible to type foreign characters in the output ISO field, because those characters are not correctly translated by MKISOFS, and therefore the file cannot be opened by ImgBurn.
F. Kill PGC Playback: The Set, SetCLnk, CSetCLnk or CSetLNK command with a Link to a cell, program or chapter were not trapped. Now, a dialog pops up to warn the user.
F. PGC Editor: Fixed a bug in the Cell preview: A wrong cell was shown after a Vob/Cell ID remapping.
F. PGC Editor: Toggling the Layer Break checkbox did not change the seamless joint flag value. This bug has been introduced in v0.6.2.
F. Command Editor - CallSS command: The option to resume at the point where the title was interupted (resume cell 0) has been removed, since this option seems illegal in all cases.
F. Remap Titlesets: The modified JumpSS-VTSM commands in the menu buttons of the VMGM were not saved during the operation.
W. Workaround for the pskill.exe problem with McAfee antivirus. It is now encrypted in the standalone executable, so that McAfee doesn't complain. McAfee may still complain when the real file is scanned in the bin folder.


DVDShrink plugin v1.4 released!
DVDShrink Remote Buttons: Added the options to use the Prev Chapter button and/or the Return button to go back to the beginning of the previous title

[bourtzovlakas]

:thanks: :thanks: :thanks:

[[Tobi]]

I cannot send mail, therefore here...


The bug with the "Cancel" button in the Select Layer Break window is there again.

[jeanl]

r0lZ,
Thanks for the release! The menu killing feature is awesome! That's 4 or 5 guides that just became obsolete! Really cool! I'm impressed!
jeanl

[r0lZ]

Thanks.
But I have to release a new version! Tobi is right. There is a bug in the Burn DL DVD GUI.