runtimeerror 7

[xebolon]

Hi Community,
this is my first post in this forum, normally I post in the german doom9-forum, but nobody can help me.
Sorry for my bad english.

I ever get a runtime-error 7, if I encode a film with RB.
Last, I encode The Fellowship of LOTR and got in the rebuild-phase this runtime-error -message.

I do everything to solve the problem, I made total new setup of RB and CCE, but nothing helps.

My OS is WIN98SE, RB 1.00 RC 5.1, CCE 2.67 trial, avisynth 2.55 of the installer-package and when I am encoding a film nothing is running on my system, I kill any process.

I encode the original scouce, I rip with DVD-Dec****er in in file-mode. I have this problem since I use the RB 1st-versions. I have compared everything with the guides and can´t find an error in the settings.

I hope anyone use WIN98SE too and can help me.

greets Xebolon

[jdobbs]

Out of Memory? Hmmm... that's really odd. I'm not sure about Windows 98SE... that's a really old operating system. It's possible I may be making a call somewhere that isn't supported by '98.

[theclaus]

Off Topic

It amazes me the people that use Win98SE still. I have a test system that has 98SE on it that I can try with RB regular but jdobbs may be right about calling something that doesn't jive with 98SE.

[xebolon]

Hi all,
I think many people use WIN98 and for this users is the RB the best way to encode their DVDs, because RB doesn´t produce files < 4GB, like DVD2DVD-R or DVD2SVCD do.

I have 256 MB RAM, windows controls the virtual memory itself, nothing is running in the background.

RB crashes in the rebuild-phase with runtime-error 7. When I klick the OK-button of the error-message - RB close and do not rebuild the segment. When I start rebuilding a second time RB crashes at the same segment. It´s the same, when I start my PC in save-mode and start rebuilding again.

Has anybody an idea.

cu Xebolon

[xebolon]

@jdobbs

I think that was a very poor answer, thank you for your engagement. I understand, my problem isn´t mainstream.

cu Xebolon

[jdobbs]

:confused:

As I always do -- I will try to find the problem. I thought that was implied in my answer.

[xebolon]

Sorry, it was a misunderstanding, I thought that was it.

cu Xebolon

[jdobbs]

Could you please send your REBUILDER.INI, REBUILDER.INF, AND REBUILDER.LOG files to dvd-rb@dvd-rb.com? I'd like to try and find out exactly where it is happening.

Thanks.

[xebolon]

@ jdobbs

Thank you for your interess, I can do it next monday, because I am working out of my hometown this week.

cu Xebolon

[xebolon]

@jdobbs

Now I tried out to rebuild the same encoded files with other versions of RB. 1.5.1 crashes at 54,4%, 0,94free, 0,94pro and 0,93free at 75,4%.

It´s allways the same, if I use original-scource-files or not.

I think this is very strange. Possible it is a problem of my system. But all analysing-tools can´t find a mistake.

cu Xebolon

P.S. Now I have an idea. My first running installation was made without Rockas installer and I only update the exe-files of the RB-versions. For the 1st versions I use the installer. I try to install it by hand oncemore. It may be a chance.

good night Xebolon

[Rockas]

Just another 2 cents... have you tried to defragment your disk? or a scandisk?
Maybe you are having troubles with virtual memory... some bad sector!?!?!?

[xebolon]

Hi Rockas,

I run defrag and norton-systemworks weekly. For troubleshooting, I let run scandisc, too. The tools can´t find any problem.

Yesterday in the evening I made a viruscheck - no virus found.
Than I test the system with Spybot - it has found malware:
PS-Guard - made 65 mistakes in the registry. Possible that was it.

At weekend I try to use RB once more.

cu Xebolon

[xebolon]

Hi all,
that was the solution!

The Virus smitfraun has destroid my registry. I worked one month to repair the mistakes it have done. Spybot with the aktual definitions has found the demaged entries in the registry. Than three registry-tools do the work. Now everything is running execelent. It was no bug in RB. It is running perfect.

cu Xebolon

[jdobbs]

That's a relief... what a nightmare!

[xebolon]

@jdobbs

Hi jdobbs, I have udated to RB 1 RC6 and I got a new error-message in the rebuild-phase: DVD-Rebuilder experienced an error updating NAVPACK 00038 00007.

Last week I have encodet 2 DVDs, without subtitles, and everything has worked perfekt. At the weekend I wanted to test LOTR Part 1 once more and got this error-message. Original-scource, movie-only, 1 subtitle ( elbish).

I can´t understand why. Is it possible, that mscomctl.ocx is the reason? I copied it to the windows-systemfolder after the first error-message and than tried to rebuilt a second time.

Sorry for my bad english, I hope you understand what I mean.

ERRlog.txt:
[08:40:09] 00038 00007 updating NAVPACK.
[12:17:31] 00038 00007 updating NAVPACK.

Rebuilder.ini:
[Options]
CCEAQM=1
Mode=1
OneClick=0
ReduceOpt=0
NoWarn=1
AdditionalOutput=1
LogFile=1
QuEncHQ=1
EncoderMinimized=0
RemoveDTS=1
HC_Quality=1
HC_Matrix=1
SkinVersion=8
CCE=3
AVSFilter01=#t = GripCrop(720,576,overscan=1)
AVSFilter02=#a = width(t)%8
AVSFilter03=#b = height(t)%8
AVSFilter04=#Crop(t,(a/2)*2,(b/2)*2,0-a+((a/2)*2),0-b+((b/2)*2))
AVSFilter05=undot()
AVSFilter06=#Convolution3D(0,3,4,3,4,2.8,0)
AVSFilter07=asharp(2,4)
AVSFilter08=ConvertToYUY2()
AVSFilter09=#AddBorders((720-width)/2,(576-height)/2,(720-width)/2,(576-height)/2)
Skin=Rockas Original
QuEncodeType=0
DVD_Label=INPUT
DVD_Name=INPUT.ISO
MovieOnly=1
HalfD1=00
Convert_16_9=00
DisableInterlace=00
iDCT=7
ConvertToYUY2=0
AudioDub=0
GOP=2
DCPrec=1
RemoveDC=1
MainMatrix=MPEG Standard
Completed=3
LowMatrix=5-Medium_Medium(2800-3500)
[Paths]
QuEnc=C:\DVD\DVDrebuilder\Encoders\QuEnc\QuEnc.exe
ReJig=C:\DVD\DVDrebuilder\Encoders\ReJig\ReJig.exe
HC=C:\DVD\DVDrebuilder\Encoders\HC Encoder\HCbatch.EXE
ProCoder=C:\DVD\DVDrebuilder\Encoders\EclPro\EclPro.exe
DECOMB=C:\DVD\AviSynth 2.5\plugins\Decomb521.dll
MPEG2DEC=C:\DVD\DVDrebuilder\DGDecode.dll
Working=C:\DVD\work\
Output=C:\DVD\OUTPUT\
CCENEW=C:\DVD\CCE267\EclCCE.exe
Source=C:\DVD\INPUT\

[CCEOptions]
VBR_bias=15
Quality_prec=20
eclPasses=4

[Setup]
Languages=1111111111111111111110111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
sLanguages=1111111111111111111110111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111

[Audio]
Selected=100

[Subpictures]
Selected=00001

REBUILDER.log:
-----------------
[15:29:25] Phase I, PREPARATION started.
- CCE SP ECLCCE encoder selected.
- AVS Filters are enabled.
- "CCE Adaptive Quantizer Matrices" is enabled.
- "Movie Only" mode is enabled.
- VTS_01: 3.619.043 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 256.599 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 66,6%
- Overall Bitrate : 3.081Kbs
- Space for Video : 3.860.590KB
- HIGH/LOW/TYPICAL Bitrates: 4.429/1.962/3.081 Kbs
[15:43:08] Phase I, PREPARATION completed in 14 minutes.
[15:45:47] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Creating M2V for VTS_01 segment 26
- Creating M2V for VTS_01 segment 27
- Creating M2V for VTS_01 segment 28
- Creating M2V for VTS_01 segment 29
- Creating M2V for VTS_01 segment 30
- Creating M2V for VTS_01 segment 31
- Creating M2V for VTS_01 segment 32
- Creating M2V for VTS_01 segment 33
- Creating M2V for VTS_01 segment 34
- Creating M2V for VTS_01 segment 35
- Creating M2V for VTS_01 segment 36
- Creating M2V for VTS_01 segment 37
- Creating M2V for VTS_01 segment 38
- Creating M2V for VTS_01 segment 39
- Creating M2V for VTS_01 segment 40
- Creating M2V for VTS_01 segment 41
- Creating M2V for VTS_01 segment 42
[07:59:19] Phase II ENCODING completed in 974 minutes.
[08:01:51] Phase III, REBUILD started.
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Rebuilding seg 6 VOBID 1 CELLID 7
- Rebuilding seg 7 VOBID 1 CELLID 8
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Rebuilding seg 23 VOBID 1 CELLID 24
- Rebuilding seg 24 VOBID 1 CELLID 25
- Rebuilding seg 25 VOBID 1 CELLID 26
- Rebuilding seg 26 VOBID 1 CELLID 27
- Rebuilding seg 27 VOBID 1 CELLID 28
- Rebuilding seg 28 VOBID 1 CELLID 29
- Rebuilding seg 29 VOBID 1 CELLID 30
- Rebuilding seg 30 VOBID 1 CELLID 31
[08:40:09] 00038 00007 -- error updating NAVPACK.
Aborted.
[11:43:50] Phase III, REBUILD started.
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Rebuilding seg 6 VOBID 1 CELLID 7
- Rebuilding seg 7 VOBID 1 CELLID 8
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Rebuilding seg 23 VOBID 1 CELLID 24
- Rebuilding seg 24 VOBID 1 CELLID 25
- Rebuilding seg 25 VOBID 1 CELLID 26
- Rebuilding seg 26 VOBID 1 CELLID 27
- Rebuilding seg 27 VOBID 1 CELLID 28
- Rebuilding seg 28 VOBID 1 CELLID 29
- Rebuilding seg 29 VOBID 1 CELLID 30
- Rebuilding seg 30 VOBID 1 CELLID 31
[12:17:31] 00038 00007 -- error updating NAVPACK.
Aborted.

Rebuilder.inf:
-----------------
[15:29:25] Phase I, PREPARATION started.
- CCE SP ECLCCE encoder selected.
- AVS Filters are enabled.
- "CCE Adaptive Quantizer Matrices" is enabled.
- "Movie Only" mode is enabled.
- VTS_01: 3.619.043 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 256.599 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 66,6%
- Overall Bitrate : 3.081Kbs
- Space for Video : 3.860.590KB
- HIGH/LOW/TYPICAL Bitrates: 4.429/1.962/3.081 Kbs
[15:43:08] Phase I, PREPARATION completed in 14 minutes.
[15:45:47] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Creating M2V for VTS_01 segment 26
- Creating M2V for VTS_01 segment 27
- Creating M2V for VTS_01 segment 28
- Creating M2V for VTS_01 segment 29
- Creating M2V for VTS_01 segment 30
- Creating M2V for VTS_01 segment 31
- Creating M2V for VTS_01 segment 32
- Creating M2V for VTS_01 segment 33
- Creating M2V for VTS_01 segment 34
- Creating M2V for VTS_01 segment 35
- Creating M2V for VTS_01 segment 36
- Creating M2V for VTS_01 segment 37
- Creating M2V for VTS_01 segment 38
- Creating M2V for VTS_01 segment 39
- Creating M2V for VTS_01 segment 40
- Creating M2V for VTS_01 segment 41
- Creating M2V for VTS_01 segment 42
[07:59:19] Phase II ENCODING completed in 974 minutes.
[08:01:51] Phase III, REBUILD started.
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Rebuilding seg 6 VOBID 1 CELLID 7
- Rebuilding seg 7 VOBID 1 CELLID 8
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Rebuilding seg 23 VOBID 1 CELLID 24
- Rebuilding seg 24 VOBID 1 CELLID 25
- Rebuilding seg 25 VOBID 1 CELLID 26
- Rebuilding seg 26 VOBID 1 CELLID 27
- Rebuilding seg 27 VOBID 1 CELLID 28
- Rebuilding seg 28 VOBID 1 CELLID 29
- Rebuilding seg 29 VOBID 1 CELLID 30
- Rebuilding seg 30 VOBID 1 CELLID 31
[08:40:09] 00038 00007 -- error updating NAVPACK.
Aborted.
[11:43:50] Phase III, REBUILD started.
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Rebuilding seg 6 VOBID 1 CELLID 7
- Rebuilding seg 7 VOBID 1 CELLID 8
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Rebuilding seg 23 VOBID 1 CELLID 24
- Rebuilding seg 24 VOBID 1 CELLID 25
- Rebuilding seg 25 VOBID 1 CELLID 26
- Rebuilding seg 26 VOBID 1 CELLID 27
- Rebuilding seg 27 VOBID 1 CELLID 28
- Rebuilding seg 28 VOBID 1 CELLID 29
- Rebuilding seg 29 VOBID 1 CELLID 30
- Rebuilding seg 30 VOBID 1 CELLID 31
[12:17:31] 00038 00007 -- error updating NAVPACK.
Aborted.


cu Xebolon

[jdobbs]

You may want to virus scan again -- that error means you ran out of memory (same as you happened before), it just get's captured now (I'm locking down errors in preparation for v1.00).

I don't see any relationship to the .OCX -- what makes you think that may be involved?

[xebolon]

Hi jdobbs,

I don´t know what for mscomctl.ocx is need, that´s why I ask you.

cu Xebolon

[xebolon]

Hi jdobbs,

I got an idea for troubleshouting for runtime-error 7.

Windows 98SE isn´t supported by microsoft any more.
So any new runtime-librarie is only tested for win2000 and winXP.
I think that some new programms, I mean not the RB, install runtime-libraries that are not 100% kompartible with Win98SE and overwrite the olders .

So my question is, witch libraries uses the RB for his work?
If I know that, I can try to change them to the originals.

Thanks Xebolon

[jdobbs]

There are many, many libaries supported. Many of them aren't directly referenced in DVD-RB but are referenced through other O/S calls.... I'm not sure I could come up with a reliable list.

[xebolon]

Ok, the other way round.

Is there a librarie witch must handel large tabels in the rebuild-phase? For updating the NAV-packs?

[jdobbs]

No library, but DVD-RB does use quite a bit of memory in arrays for the rebuild phase. Nothing that challenging, though -- and theoretically you should never run out, as Windows will start swapping to disc...

I think, though, that the "Out of Memory" error is a one of the "defaults" with MS... when all else fails it kicks out this message.

[xebolon]

@jdobbs,

possible here is a solution for the problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q190511#appliesto

But I didn´t understand it. I only user, not coder.

I wish you a good weekend

Xebolon

[jdobbs]

I don't think that is related.

I still think the problem is unique to your machine. No one else has reported or confirmed it.

A good weekend to you as well.

[Carpo]

if i remember rightly win98 was a bigger pain in the arse for wanting ram than win95 was - im guessing it could be just that - the os wants all the mem it can get and so does the encoder you use in dvd-rb (not too mention the vid card sound and all the other bits and pieces running in the background)

mind you it could be something totaly different :p

[xebolon]

good morning community,

I think it isn´t a problem of less ram, I have analysed it with freemem. Ever when RB is crashing, there is nearly 50% of memory free. It doesn´t matter if anything is running in the background or not.

Can that be a problem of the 1MB main-memory? Win98SE is a komfortable interface for DOS, not a real OS.

Or can it be a problem of strange scource, with some errors. But this would be very odd, because I test RB with different DVD´s of the same film.

Is there any tool to control, if the ripped files are valide?

PS: @Carpo, your signature tells the trouth about me;)

cu Xebolon

[xebolon]

Hallo all,

today I made an other test with the rebuider. I made a run with 0% compression, movie only; to test if the encoder produces invalide files. But I got the same error-message at 52% of the rebuilding-phase. I think this is strange.

I can´t understand why nobody can say something about the system-requirements, only poor information about used dll´s, versions of mediaplayer, etc.

RB is very experimental, not a real product. It shoud be a openscource-project, like avisynth and the other components.

cu Xebolon

[jdobbs]

Just what I need, another freaking "expert".

Have you wondered at all why you are the only person on the planet getting this error? Have you wondered why it went away when you cleared the virus the first time? Have you noticed that the only person bringing up DLLs as the possible solution is you?

As I said earlier the problem is your system. It could be questionable memory, motherboard, processor, anything... encoding puts a lot of demand on a system. But unfortunately I can't fix it for you long distance.

I've been cordial with you up until now. But here's the bottom line: RB seems to work fine for everybody but you. How many other "Out of Memory" errors have you seen reported? Has anyone said "I can confirm that."?

I have an excellent idea. Use something else... and leave me alone from now on.

[Carpo]

i still reckon its cus of low mem in that machine - 256meg is not enuff to run win98 (plus its 7 years old and not supported by MS) - when i had win98 i had 512 meg in there and still ran into probs - i would suggest you update the OS (if poss) if not use a diff method of backing up your dvds - cus i have 2GB ram in here and even so cce takes up to 800 meg of that while encoding and about 50% of cpu.

low mem in the pc and an old unsupported OS (even by the vendor).........

[jptheripper]

yeah i think we are at the point, 7 years alter and since support is dropped by the vendor, that win98 should not be supported anymore, ever. It just slows development

[xebolon]

from the freaking expert @jdoobs,

don´t tell me, I am the only one in the world who gets this error.

Look here and read your own expert-answers.

http://forum.doom9.org/showthread.php?t=91172&page=1&pp=20&highlight=error+7

cu freaking expert

[jptheripper]

um.. that was solved by reinstalling (i.e. user error was corrected)

reinstall with the installer, rerun, and if you still get the error, then post

insulting the author of the program (i.e. the only one that might fix it for you) is the wrong path to take

[jdobbs]

from the freaking expert @jdoobs,

don´t tell me, I am the only one in the world who gets this error.

Look here and read your own expert-answers.

http://forum.doom9.org/showthread.php?t=91172&page=1&pp=20&highlight=error+7

cu freaking expertSo are you really trying to make a point by referring to a post that was reported over 30 versions ago -- that was also reported to be fixed by a simple reinstall...

Get a life.

As I said... you're on your own. A bright guy like you could surely figure out a fix. Of course when you do you will find it has nothing to do with DVD-RB...

[xebolon]

OK, once more and step by step!
I can not understand, why your reaktion is so paranoid.
I am a beta-tester of your programm - right?
You are the coder of this programm - right?
Next time you will distribute a commercial version of this programm - right?
I, the beta-tester, tell you that I get an error-message -right?
You say, that is a problem of my system -right?
I ask you for the needed runtime-librarys to verify the error - right?
You only say, that there are many of them - right?
It is possible that one or more dll´s on my system are invalide, misssing, incompatible or not correct registered? - right?
The dll´s belong to my buggy system - right?
For heavens sake, what are the requirements of you programm?
What will you tell your customers, when they ask you?
Make your homeworks.

cu freaky expert

[jptheripper]

the requirements of the program is a stable system. Yours is not, as is evidenced by this particular error. It is not jdobbs job to diagnose errors on your system, that is up to you to fix independently

[feedback]

"Wah! It doesn't work. Leap through 10,000 miles, read my mind, take over my body and fix it for me because I can't be bothered to read the basic trouble shooting skills guide and the Q&A".

The above is a quote posted by 'dvd2svcd'.

I thought it might be suitable to post here regarding DVD-Rebuilder Pro. whiners.

Regards,:)

P.S. jdobbs, can't you leap through 10,000 miles and read minds? ;) :D

[xebolon]

@ jptheripper
jdobbs must not find the error on my system.
He only shoud give my the system-requierements, than I can verify the mistake. A system is stable up to the moment it crashes; you understand what I mean?
jdobbs codes with his system and everything what is running, is the standard. If he wants to be compartible, he must look for other OS.
cu freaking expert

[jptheripper]

that is not the standard. if that is the case, the thousands of users ssystems are all the standards. I have rebuilder running on 6 of my machines, all different setups, and it runs on all of them. YOu want a list of every dll I have installed?

saying your system is stable until in crashes, no kidding, it cant be any other way. That is like saying you werent a murderer right up to the point where you shot the guy.

reinstall your OS (2000, NT or XP only as those are the only ones supported mb Microsoft), and reinstall rebuilder with the installer. It will work, it has for 1000s of others.

this is the solution to your problem. If you choose to ignore the the solution, we can not help you further, as you will have chosen to not be helped.

[feedback]

Another of my favorites by the great 'dvd2svcd' is....

"do not change versions of software. We will put a Voodoo curse on you, your dog, and your goldfish".
:D
Now we could use this one for people who use incorrect versions of AviSynth, and DGDECODE for DVD-RB.

Maybe even use the Voodoo curse for the people that screw up while PreProcessing and then come crying about a bug in Rebuilder after their movie won't play.

Regards,:)

[jdobbs]

@Xebolon

You are obviously one of those people we all know and love. You are convinced your are right, and no amount of logic, common sense, or technical fact will sway that belief, so I won't try. For the others who may be reading this, here are the facts:

1. xebolon is the only person who is experiencing this "out of memory" error -- which is known to all to be one of Microsoft's infamous default errors that is used in lieu of throwing their hands in the air and shrugging their shoulders.

2. It is happening on an unsupported operating system that is 7 years old. (Microsoft won't even send out security patches or accept bug reports for it any more).

3. It cannot be confirmed by any other user.

4. It happened shortly after a previous report of the exact same error on the same machine that mysteriously went away after a "virus" was cleared.... without, by the way, any changes to DVD-RB.

5. Instead of acting as a beta tester -- he has decided I am his personal system debugger -- and makes insulting comments to try and fuel the fire.

6. Short of throwing down chicken bones, reading tea leaves, and trying to program around the phases of the moon and sun spots -- I'm not sure what I can do to fix his computer.

I encourage the reporting of problems... and a review of this forum will prove that I respond and correct them when they are valid. But when all the evidence points to a systemic problem -- it is beyond the scope of DVD Rebuilder and I can't continue to chase ghosts...

This is my last word on this subject... I hope it ends here.

[xebolon]

@jdobbs,
you are only ironical.
Nothing that helps. You do not understand what I write to you. learn reading.

[jptheripper]

@xebolon - are you kidding?

english is obviously not your first language, but that aside. Irony has nothing to do with it, you have chosen the wrong word.

and you just displayed the root of the problem. He didnt understand what you wrote, so your solution is for him to learn reading.

may i suggest, since he didnt understand the jibberish (my judgement) you wrote, that you should learn writing? the same philosophy will fix your runtime error as well.

[Carpo]

i think is starting to get a bit out of hand now - maybe a mod should close it ?

[xebolon]

@all mods
please censor my opinion. Oportunists are welcome.

cu freakling expert