What where the problems with TyTool and WinXP?

[jdiner]

Alright. I at long last have an XP machine to try and test these things on. Several people reported problems with XP over the last several months. I wrote some down but I can tell just from looking at the list that I don't have them all.

So if those that were having problems want to chime in here I will see what I can do about getting them fixed in short order.

--jdiner

[ttabbal]

I use XP and have not noticed any problems... I've extracted, cut, made VOBs, and DVD images from TyTool 7r3 without trouble. I know it's an old version, I'm going to test the latest version shortly.

[Pro-289]

There's nothing in Help->About.
The Edit options don't work.
But I guess you already know about these. :)

[jdiner]

I was talking about crashes. Not unimplemented features. Those are found across any version of windows.

Some time ago people were complaining that "something" was causing TyTool to punt on load up every time.

--jdiner

[newbie]

There was thought to be a problem with tystudio (beta) and XP but it turned out the problem was with all WIN.

I don't recall seeing any XP specific problems posted with tytools.

[Generiq]

I have had Tytool 7r6 close twice while downloading the now showing list.

[jdiner]

Hummm. That is wierd. Did you get the .txt file in c:\ that had the nowshowing data in it? If you have that from when it closed I would like to see it.

--jdiner

[jdiner]

Originally posted by newbie
There was thought to be a problem with tystudio (beta) and XP but it turned out the problem was with all WIN.

I don't recall seeing any XP specific problems posted with tytools.
I am uninterested in issues with tystudio as I am not involved with it.

I was looking for TyTool issues. They must have come in PM's that are now gone from my box... :(

--jdiner

[newbie]

Originally posted by jdiner
I am uninterested in issues with tystudio as I am not involved with it.

I was looking for TyTool issues. They must have come in PM's that are now gone from my box... :(

--jdiner

I KNOW THAT I thought the tystudio POSTS may have been the ones you remembered.

[Vegas]

Not sure if this is XP related, but thought I would start here.
I have a ty stream that processes (make key) about 1/3 of the way through and then crashes Tytool. This is only the 2nd stream out of about 30-40 that this has happened with.
I have tested the stream with Tytool7r3 - 7r6 with the same result.

Here is the log from Tytool.

Detected Tivo Type: Series2
Detected Audio Stream Type: MPEG Layer II
Final standardAudioSize = 592
Final standardFrameLength = 576
Final standardAudioDiff = 2160 or 00:00:00.024
First Video PTS: 00:04:14.769
......... 100......... 200......... 300......... 400......... 500

......... 600......... 700....Unknown PES packet. Fix it dear henry...
type = 0x1

Found an OOB packet... The Video Diff is: 00:11:16.340
BBB the PTS was bad, but the new SEQ check lines up|!?
Found an OOB packet... The Audio Diff is: 00:00:00.024
It is in sequence... Everything is fine...
Unknown PES packet. Fix it dear henry...
type = 0x1

At this point I get the "Tytool must close window"

BTW, thanks jdiner, for the great tools.

[POTI]

I have not seen any issues with the new version and XP JDiner... Love the program!

[jdiner]

Originally posted by newbie
I KNOW THAT I thought the tystudio POSTS may have been the ones you remembered.
Oh know. It was definately a TyTool message. I doubt I have read 4 total posts dealing with TyStudio...

Ummm. I just don't remember who posted it. Fugg maybe? Crap. It was an older timer here on the thread. oh well. Either they will chime in or I will not worry about it.

--jdiner

[jdiner]

Originally posted by Vegas

......... 100......... 200......... 300......... 400......... 500
......... 600......... 700....Unknown PES packet. Fix it dear henry...

At this point I get the "Tytool must close window"

BTW, thanks jdiner, for the great tools.

Wow. I haven't seen one of those in a very long time. From what you posted do:

TyFileSplit <file.ty> prob.ty 710 50

and send me prob.ty.

If you can put it up somewhere were I can get it PM me with detail. Otherwise I will send you some ftp site information.

Shouldn't take too long to get a fix for it.

--jdiner

[BubbleLamp]

I'm on my last day of vacation in NY, but from memory the two issues I recall were:

1) A greater tendency to negotiate the link in such a way that you got piss-poor performance. (Any luck with the latest info I sent you?)

2) Delete would always crash the app (not sure if that was XP related, but it was a pet peeve of mine :eek:)

[jdiner]

Originally posted by BubbleLamp
I'm on my last day of vacation in NY, but from memory the two issues I recall were:

1) A greater tendency to negotiate the link in such a way that you got piss-poor performance. (Any luck with the latest info I sent you?)

2) Delete would always crash the app (not sure if that was XP related, but it was a pet peeve of mine :eek:)

Oh yeah. That is what I was looking for. It was the delete call that crashed it. Redo'ing that all the way around this morning. So it should be back and ready to use...

--jdiner

[Pro-289]

Just found a bug in the GOPEditor that comes with TyTool7r6 & 7r7a. It seems to be Windows related, since 98SE & XP both cause it.

Run GOP Editor
Select File->Open KeyFrame File...
Select Cancel or the X
Select File->Open KeyFrame File...
Select Cancel or the X
Select File->Open KeyFrame File...
Select Cancel or the X
Select File->Open KeyFrame File... (Then it crashes) :eek:

Don't ask me why the hell I was opening and canceling. I was bored. :p

[thedroid]

Originally posted by BubbleLamp

2) Delete would always crash the app (not sure if that was XP related, but it was a pet peeve of mine :eek:)

Same problem I have:
After deleteing the program would crash once out of every 2-3 times, after trying to get the now showing list.

[jdiner]

Well. That sucks.

I will have to look at why.

Can't think of anything that should crash it because of doing that. But I will look.

--jdiner

[Prof. Honeydew]

(TyTool7r7 under XP pro)

1. Take a downloaded .ty file
2. File->Process Make Key File(s)
3. Edit KeyFile(s)

Results in:

GopEditor.exe has encountered a problem and needs to close.

Also running the GopEditor.exe directly directly gives the same problem when trying to a ^O (File->Open KeyFrame File) and choosing one of the .ty files that were downloaded). Will result in a crash.

[Prof. Honeydew]

Hmm... I may have jumped the gun. I just tried another .ty file and that one seems to be run under the GopEditor.

So there was something with my other .ty file that the GopEditor didn't like. BTW- these files can from a HDVR2)

[hashed]

7r8 is crashing after successfully connecting, while downloading the nowshowing list... giving this in the c:\nowshowing.txt



Calling NowShowing.tcl:
<166>Aug 7 15:36:17 tcl[24555]: Tcl created pool of 1458176 bytes


Calling NowShowing.tcl:
<166>Aug 7 15:38:23 tcl[24556]: Tcl created pool of 1458176 bytes


Calling NowShowing.tcl:
<166>Aug 7 15:40:04 tcl[24560]: Tcl created pool of 1458176 bytes
retrying after errTmBackgroundHoldoff ...


Calling NowShowing.tcl:
<166>Aug 7 15:41:44 tcl[24562]: Tcl created pool of 1458176 bytes

-------------
something else flashes up in the bottom box just b4 7r8 closes, but i cannot tell what it says.
Thanks

[hashed]

Ok, the issue there was the NowShowing.tcl file... got it fixed!
I don't know that I completely understand the process of making the DVD's - a movie is pulled down in, say, 5 files... does the vob-mux process combine them into one file to put onto a dvd?

[jdiner]

hashed:

Do you still have the c:\nowshowing.txt file on your harddrive? It is saved out by the TyTool program... I have been waiting for someone to see this again so that I can look at the output and try to figure out what is going on there.

If you have it please zip the file and post it up here, and also what specifically did you do to fix it?

--jdiner

[TiVOBell]

FYI. I get this

EDIT: message is "GopEditor.exe has encountered a problem and needs to close."

(see attached screenshot) when trying to edit Key Files on a 3.8 GB file.

I will try with a smaller file to see if it happens again.

WinXP P4 2GHZ 512MB RAM 60GB free on C:

[newbie]

Not sure if this quote from Newsday may reflect some of the difficulties some people are having with XP PRO.


[QUOTE]Q. I'd like to temporarily connect my two computers (both running XP Professional) to transfer files by connecting their network cards with a crossover patch cable. I would like to do this without a router since I only want to quickly transfer files once. My attempts with the networking wizard have been unsuccessful. Is this possible?

A. In theory, yes, but I've seen some traffic on the Net that suggests this setup is particularly sensitive to minor cable irregularities and network interface card incompatibilities. You might want to try another type of cable too, since you can network with serial (null-modem), parallel or USB cables.

[TiVOBell]

As a follow-up to my post, the same thing happens with a ~680MB TY file.

This is an SA S2 4.0.

[jdiner]

Originally posted by hashed
7r8 is crashing after successfully connecting, while downloading the nowshowing list... giving this in the c:\nowshowing.txt


Calling NowShowing.tcl:
<166>Aug 7 15:36:17 tcl[24555]: Tcl created pool of 1458176 bytes

Ah. Excellent. This is why I left the c:\nowshowing.txt bit in there. I will get a fix in place for the next release of TyTool.

--jdiner

[jdiner]

Originally posted by TiVOBell
FYI. I get this

EDIT: message is "GopEditor.exe has encountered a problem and needs to close."

(see attached screenshot) when trying to edit Key Files on a 3.8 GB file.

I will try with a smaller file to see if it happens again.

WinXP P4 2GHZ 512MB RAM 60GB free on C:
It is very hard to tell from your screencap but that kind of thing happens most when people load up a .ty into the GopEditor rather than a .key file.

Other than that the .key file might have been corrupt or incorrectly made.

Plus it looks like the .ty was a .ty+ from mfs_ftp. I don't know if that has an impact on things on not. I have never really used mfs_ftp.

What portion of the process with GopEditor where you in? Loading up? Saving? Editing? What...

--jdiner

[TRILIGHT]

FWIW... I am able to use WinXP with TyTool 7r8 on my DirecTiVo TY files without incident. Also, in reference to what was said earlier about a crossover cable, I am currently using a crossover cable to pull to a firewire drive connected to my laptop. Transfer is flawless. Normally, I have the unit as part of my full network but I am at my sister's house right now and there is no good way of setting up a network here without running a bunch of cable and pissing her off. hehe ;) Anyway, the crossover cable, WinXP, and TyTool 7r8 run great at an average transfer rate of about 1.5MB/s.

[jdiner]

Originally posted by rc3105
nope, the xml data is appended to the tail end of a regular mfs_stream tyfile

Ah good to know. So there should be no impact at all then. I am assuming it is less than 128k in size anyway so it would not get processed at all.

--jdiner

[TiVOBell]

It was a TY (not TY+) file from MFS_FTP. I think the .key file _was_ corrupt.

I am having other problems with TyTool that I need to resolve before I can be sure this is XP related though, so I will take this to another thread.

Thanks for the assistance - when my other issue is resoloved, I will post back here as to whether I still have the problem.

[DjPK]

I am having an odd problem when i make a key file from a 2gig streams it doesn't seem to create the entire file.

Its about 1/3 the size and when I open it in gopeditor it only has about the first 5-10 minutes.

Any Ideas.

BTW these tools are just killer!!!

Paul

[jdiner]

Originally posted by DjPK
I am having an odd problem when i make a key file from a 2gig streams it doesn't seem to create the entire file.

Its about 1/3 the size and when I open it in gopeditor it only has about the first 5-10 minutes.

Is there any text output? Anything in the results textedit that shows what was going on. There is just no where near enough information here for me to do anything.

--jdiner

[DjPK]

I was able to fix this by upgrading to the newest version. It was a windowsxp + sp 1 issuse.

Thanks,
Paul

[jdiner]

Originally posted by DjPK
I was able to fix this by upgrading to the newest version. It was a windowsxp + sp 1 issuse.

Good to know. Just reminds me of why after 6 months I think... MS had spent $1bil on XP, and had make less than $300mil on sales. What a mess. With how stable 2k is I wonder how that happened.

--jdiner