Re: samdsk

1999-11-25 Thread Dave Hooper
Hi. If anyone's to blame, it's most probably me, since I actually wrote the
damn thing! :)

Um, are you *sure* it says Error 0x2000 ? I can't actually find that in my
source code ... I've also (ahem) lost the docs for samdsk and also for the C
libraries that I use ...
If anyone uses DJGPP could they tell me what the error code from the
_bios_disk function is ... and what a return value of either (0x20**) or
(0x2000**) means ... !

But yep, I'd say that running it from a genuine DOS prompt should be more
successful than running it in a DOS shell under Windows.

What SAM Format proggy?

D a v e @ s p c

- Original Message -
From: Justin Skists [EMAIL PROTECTED]
To: sam-users@nvg.ntnu.no
Sent: Wednesday, November 24, 1999 5:01 PM
Subject: RE: samdsk


 What SAM Format proggy?

  -Original Message-
  From: David Ledbury [SMTP:[EMAIL PROTECTED]
  Sent: Wednesday, November 24, 1999 4:39 PM
  To: sam-users@nvg.ntnu.no
  Subject: Re: samdsk
 
   Justin Skists wrote:
   
OK, gang.
   
SAMDSK - right...
   
What does Error 0x2000 mean? it seems to try writing the first
sector
a few times, say the error and carry on like nothing has happened.
   
Oh, I'm running it in a dos box in NT4.0 SP-something-or-other.
   
Justin.
 
  Sounds like one for Chris P
 
  I seem to remember u had to run the SAM Format proggy, quit from it and
  this enabled the Int 13 emulation or summthink




Re: OT: Java WFC Help!!

1999-11-25 Thread Nick Humphries
From: Simon Cooke [EMAIL PROTECTED]


 Panic over. Use of WFC was a panic measure - the solution was just to
program
 Java properly.


snip

WFC is not for Applets... it's for Windows programs.

I just wish VJ++'s help files documented the stuff which MS replaced in WFC.
Things like mouseOver and the like.

Nick




RE: Sam Coupe Scrapbook Updates / FAQ / WinCoupe

1999-11-25 Thread Chris Pile
 At least one person and game forgotten too, namely me!!

Done.

Cheers Tim!  I agree with everyone else, the new colourful
format is far more pleasing!


RE: samdsk

1999-11-25 Thread Justin Skists
It definitely said Error 0x2000 in the top left hand corner.

I just checked the ref guide at http://www.delorie.com/djgpp/doc/libc-2.02/
and 0x20 (in AH) means Controller failure. Hmmm

If I remember rightly, the program gave 9 boxes and an X for each track.
My SAM certainly did not like booting the resulting disks...

Failing any attempt at getting this (work's) computer to do anything
right, can someone tell me the format of .dsk and how it maps to
a real disk using something like WRITE AT statements in BASIC. If I
have to, I'll split the .dsk file into 2 400K blocks and get my SAM to
write out the damn disk I'm determined to play with these utilities
and games that I downloaded whether it kills me or not

Justin.

 -Original Message-
 From: Dave Hooper [SMTP:[EMAIL PROTECTED]
 Sent: Thursday, November 25, 1999 12:27 AM
 To:   sam-users@nvg.ntnu.no
 Subject:  Re: samdsk
 
 Hi. If anyone's to blame, it's most probably me, since I actually wrote
 the
 damn thing! :)
 
 Um, are you *sure* it says Error 0x2000 ? I can't actually find that in
 my
 source code ... I've also (ahem) lost the docs for samdsk and also for the
 C
 libraries that I use ...
 If anyone uses DJGPP could they tell me what the error code from the
 _bios_disk function is ... and what a return value of either (0x20**) or
 (0x2000**) means ... !
 


RE: samdsk

1999-11-25 Thread Si Owen
Justin Skists wrote:
 If I remember rightly, the program gave 9 boxes and an X for each
 track. My SAM certainly did not like booting the resulting disks...

Ah, so it can't read the 10th sector.  I think you need the special version
of FDREAD to allow access to the 10th sector...


 I'm determined to play with these utilities and games that I
 downloaded whether it kills me or not

I've been using Aley's 2SAD.EXE with the -s option to convert from .DSK to
the normal uncompressed .SAD files, then using his SBK.EXE with the 'r'
command to write it back out to a real floppy.  All best done from real DOS
or Command-prompt only mode outside Win9x (not on NT!).  Both those
utilities can be found in:
ftp://ftp.nvg.unit.no/pub/sam-coupe/emulation/simcoupe/SimCoupe079_DOS.zip

It shouldn't be long before you can do it all from within WinCoupe, by
selecting the source .DSK image in one drive and the real floppy drive in
the other, then just doing a normal SAM disk copy between them...

Si



RE: samdsk

1999-11-25 Thread Justin Skists
 I'm determined to play with these utilities and games that I
 downloaded whether it kills me or not

I've been using Aley's 2SAD.EXE with the -s option to convert from .DSK to
the normal uncompressed .SAD files, then using his SBK.EXE with the 'r'
command to write it back out to a real floppy.  All best done from real DOS
or Command-prompt only mode outside Win9x (not on NT!).  Both those

Si,

Thanks for the tips. I have just rebooted back into NT4 from DOS
after your advice. New disks have been created and they seem to
display the directory with Aley's SMD program.

Maybe I should've checked that samdsk worked whilst I was in
DOS mode...

I want to play with them, now! :)


It shouldn't be long before you can do it all from within WinCoupe, by
selecting the source .DSK image in one drive and the real floppy drive in
the other, then just doing a normal SAM disk copy between them...

If I had so much trouble with this from NT4. How is doing it all
from WinCoupe going to help it any better?

Justin.


Re: OT: Java WFC Help!!

1999-11-25 Thread Simon Cooke
From: Nick Humphries [EMAIL PROTECTED]
 WFC is not for Applets... it's for Windows programs.

 I just wish VJ++'s help files documented the stuff which MS replaced in
WFC.
 Things like mouseOver and the like.

Er... what like? There aren't any.

The only differences are:
Addition of a ton of packages that begin with com.ms.* (specifically, for
WFC, you're interested in:

com.ms.dll (J/Direct)
com.ms.win32.* (J/Direct win32 wrappers)
com.ms.wfc.* (WFC framework api)

added: delegate and multicast keywords (which if you've installed Visual
Studio SP3, aren't enabled by default - nor are the J/Direct @doc comment
hints)

Other than that, *NOTHING ELSE* has been changed (and nothing has been
replaced). Nothing in java.* has been altered. The MS JVM supports up to and
including Java 1.1 (but without some of the extension libs, which were
optional). No later versions can be included due to legal disputes with Sun
over things like WFC et al.

Simon
--
Clairvoyeurism - the supernatural ability to predict what someone will look
like naked.




Re: samdsk

1999-11-25 Thread Simon Cooke
From: Justin Skists [EMAIL PROTECTED]
 It shouldn't be long before you can do it all from within WinCoupe, by
 selecting the source .DSK image in one drive and the real floppy drive in
 the other, then just doing a normal SAM disk copy between them...

 If I had so much trouble with this from NT4. How is doing it all
 from WinCoupe going to help it any better?

Using the Windows NT/ Windows 98 device driver dev kit and writing a
filesystem driver for it? :-)

Simon



RE: samdsk

1999-11-25 Thread Si Owen
Justin Skists wrote:
 If I had so much trouble with this from NT4. How is doing it all
 from WinCoupe going to help it any better?

Well, just as an abstraction layer to hide the conversion details; you can
convert between DSK/SAD/SDF and real floppy just by copying disk to disk in
the same way you would do on a real SAM.

That said, the initial support is for Win95/98 only, as NT4/2000 will
require a separate device driver to provide the functionality that the
standard floppy kernel-mode driver lacks.  It won't get done straight away,
but I'd like to see it done at some point, as the NT based versions of
Windows are the future of MS Windows.

Si



RE: samdsk

1999-11-25 Thread Justin Skists
OK ok ok ok... being a dev driver developer, I should've known that :)

Obviously, I wasn't thinking when I wrote that email! :)

Staring at endless amounts traceprintfs from a unix device driver
trying to determine where my interrupts are going (if it is
interrupts that's causing my problem) tends to fry my brain...(especially
if an inordinate amount of coffee has been consumed aswell)


Justin.

 -Original Message-
 From: Simon Cooke [SMTP:[EMAIL PROTECTED]
 Sent: Thursday, November 25, 1999 3:26 PM
 To:   sam-users@nvg.ntnu.no
 Subject:  Re: samdsk
 
 From: Justin Skists [EMAIL PROTECTED]
  If I had so much trouble with this from NT4. How is doing it all
  from WinCoupe going to help it any better?
 
 Using the Windows NT/ Windows 98 device driver dev kit and writing a
 filesystem driver for it? :-)
 
 Simon


Re: OT: Java WFC Help!!

1999-11-25 Thread Nick Humphries

-Original Message-
From: Simon Cooke [EMAIL PROTECTED]
To: sam-users@nvg.ntnu.no sam-users@nvg.ntnu.no
Date: 25 November 1999 15:27
Subject: Re: OT: Java WFC Help!!


From: Nick Humphries [EMAIL PROTECTED]
 WFC is not for Applets... it's for Windows programs.

 I just wish VJ++'s help files documented the stuff which MS replaced in
WFC.
 Things like mouseOver and the like.

Er... what like? There aren't any.


Well, there isn't any documentation in MSDN for Java event handling functions
like mouseDown(), mouseMove(), etc, etc. Highly annoying. (Yes, I know they've
been deprecated, whatever that means, but if they've been replaced, I would
like to know with what...)

Nick



Re: OT: Java WFC Help!!

1999-11-25 Thread Simon Cooke
From: Nick Humphries [EMAIL PROTECTED]
 Well, there isn't any documentation in MSDN for Java event handling
functions
 like mouseDown(), mouseMove(), etc, etc. Highly annoying. (Yes, I know
they've
 been deprecated, whatever that means, but if they've been replaced, I
would
 like to know with what...)

Ah... the changes are documented - but remember, it's *Sun* you're dealing
with here, not Microsoft - Microsoft didn't make these changes, Sun did.

The AWT event model was changed from the one mentioned above, to an event
listener model for Java 1.1 (the old one still works and probably will
forever more).

Basically, you use an EventListener object (sometimes built using an
anonymous inner class - UGH!) and bind that object to the event. Do a search
for EventListener on Sun's site, and on MSDN for more information.

Simon



SAAEmu 0.61

1999-11-25 Thread Dave Hooper
I'm a bit disappointed in Aley's SAAEmu 0.61.


1. Credit on the main screen (as requested!). Preferably immediately below
the line that says Z80 emulator by FMS  Aley Keprt, libraries by (c) FMS
1996. If possible, credit should say SAA-1099 emulator (c)1999 Dave Hooper
latest @ http://www.geocities.com/stripwax;. This is eighty characters.
2. Documentation (saaemu.rtf) should include my email address too. I'm
afraid my version of MSWord does not correctly render the crazy {HYPERLINK:
mailto:[EMAIL PROTECTED] field codes - it displays Error! Bookmark not
defined. At the very least change mine to read Dave Hooper, the author of
SAAsound: [EMAIL PROTECTED]. Maybe change the others so they are
human-readable too?
3. Ideally, your site (http://www.inf.upol.cz/~keprta/sam/saa//welcome.html)
should also mention a link to get the latest version of SAASound.dll. Even
an email address would do.
4. Are there bugs in saaemu 0.61? Every now-and-then it spews crazy rubbish
all over the screen, including messages like CPU HALTed and stuck at
PC=0099h  . Seems to happen especially when doing SAA32 tunes\enola and
playing and quitting and playing and quitting, a couple of times, and then
doing SAA32 tunes\tetris


I will shortly be releasing the source for saasound.dll (as soon as I'm
happy with it and it's in a readable state!)
D a v e