Path: chuka.playstation.co.uk!news
From: rs108@mdx.ac.uk (Robert Swan)
Newsgroups: scee.yaroze.programming.sound
Subject: .def file editing
Date: Tue, 10 Mar 1998 03:10:04 GMT
Organization: PlayStation Net Yaroze (SCEE)
Lines: 18
Message-ID: <3504ab1d.5896770@news.playstation.co.uk>
References: <35039C00.926F4898@netmagic.net> <3503C036.B79872B8@codeworks.demon.co.uk> <35047926.9140F9B2@netmagic.net>
NNTP-Posting-Host: stu-dialup10.mdx.ac.uk
X-Newsreader: Forte Free Agent 1.11/32.235

I thought I was doing well, seeing as I got my sound to work fairly
early on, but to be limited by the number of characters we can fit on
one command line? nice one.

From my sketchy understanding of sound, heres a (long winded)
question-

I've sort of figured out the .def file except I'm worried about the
importance of a few things. It says the file sizes are calulated by
the tools to create a .vh and .vb file, and yet owing to my lack of
faith in the manuals I wouldn't be surprised if it was confused after
trying to work out how mkvab operated (you use mkvab with a .def and
vags to create a .vab, but to get a .def you use mkvab on a .vab.
Hang on, chicken + egg scenario) and that the files sizes specified at
the start and end are vital. I did some calculation on the .def file
from std0 and found that the total of all the seperate files sizes
didn't match that specified at the start. If this isn't important,
then don't worry, but if it is, why the discrepency?