ChanServ changed the topic of ##yamahasynths to: Channel dedicated to questions and discussion of Yamaha FM Synthesizer internals and corresponding REing. Discussion of synthesis methods similar to the Yamaha line of chips, Sound Blasters + clones, PCM chips like RF5C68, and CD theory of operation are also on-topic. Channel logs: https://freenode.irclog.whitequark.org/~h~yamahasynths
emeb has quit [Quit: Leaving.]
<TD-Linux>
no
<TD-Linux>
but you can go into the bios by holding HELP
<TD-Linux>
you might be able to turn on nec 88 basic if you have nothing to boot from
<andlabs>
*88* basic?
<andlabs>
anyway I can get into the BIOS screen but I can't seem to get past the memory check after that
<andlabs>
my system has two floppy disk drives and an internal 10GB hard drive and I don't hear anys eeking from any of them
<andlabs>
I'll try plugging directly into the wall tomorrow
<andlabs>
in case the problem is my surge protectors don't allow the laptop to draw enough current to power the drives
<andlabs>
which would be very strange
<andlabs>
but the PSU I have ins't the original one so eh
<cr1901_modern>
ej5: It's probably unrelated to your MCA woes, but this wouldn't be the first time I've seen Wolf3D do stupid shit when trying to play sounds. So might as well paste the vid: https://www.youtube.com/watch?v=cMwykY_smR4
<cr1901_modern>
>It doesn't happen on the 386.
<cr1901_modern>
I wish I knew why...
<ej5>
the answer is in the comments of the video
<ej5>
trixter responded and said "DMA control has ports that overlap with 80h, so you're seeing the DMA transfers to the card when sound plays. Pretty cool."
<cr1901_modern>
Fair, but I still wish I knew why it doesn't happen on 386
<ej5>
i can only speculate but perhaps the card is only picking up on the "memory read" part of the DMA cycle
<ej5>
on a 386, this would be occurring on the CPU memory bus and would not show up at all on the ISA bus
<ej5>
but it could also be a timing difference between the two chipsets
<protosphere>
I think a hang at the memory check on a PC-98 means that it's trying to find something to boot from. If there's nothing to boot from mine will display a message in the centre of the screen
<cr1901_modern>
ej5: I know badly-behaved POST cards do not distinguish port address 0x80 from memory address 0x80. Is that what you mean by "memory read" part of the DMA cycle?
<cr1901_modern>
(Otherwise I THINK what Trixter means is the post card is picking up I/O writes to the DMA controller at the 0x80 range)
<cr1901_modern>
port I/O writes*
<cr1901_modern>
And why on a 386 ISA-only system would activity on the CPU memory bus not show up on the ISA bus? :P
<whitequark>
hum, writing to 0x80
<whitequark>
isn't that where the 8086 IDT is located?
<whitequark>
well, interrupt table
<sorear>
half of it
<whitequark>
half?
<sorear>
1/8, can't math, 0-0x400
<sorear>
wouldn't be the first or second thing to conflict with the IDT, more concerning is that's where the DOS syscall vector is
<whitequark>
oh!
<whitequark>
oh that explains
Xyz_39808 has joined ##yamahasynths
Xyz39808 has quit [Ping timeout: 264 seconds]
emily has quit [Quit: killed]
alva has quit [Quit: killed]
myon98 has quit [Quit: killed]
emily has joined ##yamahasynths
alva has joined ##yamahasynths
myon98 has joined ##yamahasynths
<cr1901_modern>
DOS syscall vector is int 0x21; Linux uses 0x80
<whitequark>
0x80 is the vector for int 0x20
<cr1901_modern>
Oh, right, I can't multiply :). well it would be 0x84 that's the vector. Anyways you said something about a write to 0x80; yes, that would indeed destroy the IVT
<cr1901_modern>
in the context of what I was thinking of: POST cards don't ignore READs to memory location 0x80 either
<cr1901_modern>
this makes my POST card worthless for 8088 systems where a DMA channel read cycle is used for memory refresh
<cr1901_modern>
(Oh, even better... this version completely ignores reads period :D: http://bbright.tripod.com/information/post.gif. So it has less "intelligence", yet would work better than the mass-produced card I have.)
nukeykt has quit [Remote host closed the connection]
nukeykt has joined ##yamahasynths
<andlabs>
brwosing this PC-98 disk archive, one of the games is called "Pure My Dool"
<andlabs>
so there's your game name for the day
<andlabs>
hey whitequark you were interested in that Motorola 1-bit thing
<Lord_Nightmare>
ej5: be careful with that digitizer cursor you were taking apart
<Lord_Nightmare>
i know themogminer was looking for info for reverse engineering the digitzer on the quantel paintbox
<ej5>
is that what that is?
<Lord_Nightmare>
don't break the coil! i don't know how many windings that coil is, but i think it matters
<ej5>
and yes i was careful not to break the coil
<Lord_Nightmare>
themogminer and others (and I) were looking at old summagraphics etc patents to try to figure out exactly what digitizer tech the quantel paintbox digitizer uses
<Lord_Nightmare>
it doesn't use the oldest early 70s tech
<Lord_Nightmare>
but MAYBE not the later '2 foil' tech either
nukeykt has quit [Remote host closed the connection]
Xyz39808 has joined ##yamahasynths
Xyz_39808 has quit [Ping timeout: 244 seconds]
<andlabs>
themogminer pointed me to the MAME discord when I showed them something the other day