can a dvd be ripped over a network?

[sunja]

I have one Pentium 3 with a dvd drive and a cd burner but the hard drive is small. This PC is connected to a AMD with a 30gig drive. Is it possible to rip a dvd from the Pentium 3 right over the network into the AMD and then back to the Pentium 3 to burn it?. And if so would I need any specific software to do it? Thanks to any body that can help.

<font size=-1>[ This Message was edited by: sunja on 2001-11-16 11:32:08 ]</font>

[sunja]

It's actually" "network into the AMD and then back to the P3 to burn it.

[JJamez]

Sure, its possible.

I do a similar thing, for a different reason. I use the 2nd PC to convert, so as not to tie up my main box for hours on end. My main box has the DVD-ROM.

Unfortunately, I'm using XP and the network transfer is VERY slow. I've heard of the problem before, but have yet to find a solution. It takes roughly 1/2 an hour to transfer a 700MB file.

Assuming your network doesn't have the problem mine does, it should be fine. All you need to do is set up the network, which it sounds like you have done already.

What I wound up doing is connecting the DVD-ROM to my 2nd box to rip directly to it, and after converting in TMPGE, sending the ~700MB file(s) back to my main box via the network.

[Roadwart]

Assuming the PC`s are already networked, yes. I`m assuming here that you have enough room on the P3 to store the VOB files. Run up smartripper & rip the VOBS to a partition on the P3. Once the rips complete, run up your favoured VOB to MPG/avi encoder & when you choose where to save the files, go through network neighbourhood & browse to a partition on the AMD & save the files there. once you have done that, run up your burning program on the P3 & browse through network neighbourhood again to find your MPG/AVI & then burn in the usual way. You may have to lower the burn speed depending on your network speed.

[Daywalker]

Sunja,

Hi. I used the following method to get around the issue of insufficent space on my home and office machines. Several times the past year, I have used Terminal Server to connect to machines when either I can't physically be at the workstation or if I forgot to run a batch script on TMPGEnc.

At the very least, this provides the following benefits:
1) You are not adversely affecting your main system resources by encoding processes or disk space issues. This is since all operations are done on the Terminal Server itself.
2) You can close out the Terminal Server session but not log off. Therefore, the session is still running on the Terminal Server and you can periodically re-connect and check to see when it is done. Note: This works if your Terminal Server is properly configured in regards to session time-outs.

I hope that this helps! Later!.