You have the last of the Revox A77, the MKIV. The playback boards you have are the earlier ones from a MKI, MKII.. The MKIV had plastic transistors, yours show the metal case transistors. The all work the same, no big deal. Yes, cleaning the heads really, really good helps.
Hello dear friend, is there an option to make this beautiful thing you made, but with 6 strips of 5 meters each? Of course I supply the voltage externally and not through the controller? I want to do exactly like yours but with 6 strips of 6 meters each. Waiting for your reply
Only just seen this, and I'm only about 10 minutes in - you're going to have problems with this hardware configuration! VINES wasn't really designed to use IDE drives, as it was a sever OS, and therefore the IDE driver was limited a maximum capacity of 504MB, although the same driver would work with larger capacity ESDI drives. You're better off using SCSI or a supported RAID array, which doesn't have this limitation. Many popular storage adapters are supported in the standard kernel, and others were available on floppy. The other problem is that only SCSI CD-ROM drives are supported with a base intallation. There were some ATAPI drivers available from Compaq, but they would only run on a select few Compaq server models. Earlier releases of VINES could also be installed from a stack of floppies, but this was removed by the time of VINES 8.50. Another option was to install from a tape, but you needed to duplicate this tape from a CD-ROM drive from a menu option on a running server. VINES 8.50 had quite a large selection of supported network adaptors, and it was also possible to install others once the system was up and running.
About 1hr 15 minutes in now. The kernel panic you get with VINES 8.50 is due to the IDE driver not liking a large partition. The OS was able to create the partition as it uses the BIOS to create the initial filesystem. Not sure about the panic with VINES 5.50. As it's in the ST506 driver used for the IDE drive it may be due to a large partition, or as you say it could be Cyrix related. VINES 5.00 was incredibly buggy in may ways, and was used by few sites.
Thanks for your video :) if you are wondering how to open the case, i've found this another video ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-BOqmqGzd-C8.html and it works pretty well.
I can't believe he put it together with a bad switch. Iffy at best. I would at least jumper the switch so not needed. I am working on several at this time and so far, it has been the solar cells. I am looking for a replacement now. My units use a YX8019. I can't find any difference between the -18 and - 19.
The resistor that was supplied affects the minimum current of the connected load. By default it is 45 mA or 80 mA for clones of this chip. If you solder not 0.5 ohm but 5, then the starting current from the load will be in the region of 20-30 mA.
If I did label the RAS and CAS lines wrong, I apologize. I had no reference for how they were laid out on the system. I even asked on VCFed if there was a specific way to tell which bank was Bank 0 on any XT clone. Not so with the Sanyo. Also, that portion on the 157 with the Select and Enable pins was very confusing for me, which is probably why I made the errors in the first place. I check my connections multiple times to make sure they make sense and fit together. I'll take a look at those 157's S & E pins later today to see where they connect to.
Sorry about the confusion. I left off connections on the memory, to leave the assumption that the memory inputs and outputs on the motherboard were routed like a 5160, or a clone with a similar configuration. I really appreciate that you're reverse engineering this schematic for me. Figuring out the connections on the board was just as difficult for me as it is for you building this memory-addressing simulation.
Just a quick question. If using this kind of board with eg. 7v, to compensate for heat generated by the chip, would adding a 5v Noctua fan help with cooling the board?
Fascinating - the VGA / VESA connector was one of those unused headers in a PC that no-one seemed to have a card for, great to see it in use and explained so well. Was wondering if there's any data hidden in the blanking when the palette/mode changes - i've no idea about how real ramdacs were programmed. via the data or another set of pins. Thinking about the palette - that problem must have been solved by designers using the card internally to a single pc. is there a VGA call to grab the palette values that can be made into a small TSR prog to keep track of them and save to a text file (that you could later extract and marry up to the data from the card) - probably only work for real mode software? you could try software that deliberately cycles / changes the palette quickly to see if it gives you any clues. DOS versions of Fractint had this, and also had practically every display mode you could wish for in terms of testing different modes/refresh rates. looking forward to an update.
hi good video but from my understanding you can not push power backwards on these leds hence the reason for the arrows data power and live power would push forward only. for you to power inject you would do that half way down equaling out the power usage . i have done all of mine on a larger scale my largest is 1,476 led's matrix i power injected 2 times i used a esp32s chip and boosted the data line with a low level converter 3.3v to 5v jump as data pushes at approx 3.3v this helped with glitches as this is on a large scale works seamlessly hope this helps . My power booster is a 60amp power supply it doesn't use that much but i also use that for my led singing Christmas bulbs.
I have a vfx1 headgear it works on ATI mach 64 but dosnt ,wor on voodoo3dfx v5, I wasn't able to find the reason,got another card Ati rage pro, it didn't work,then an ati 3d rage pro agp 2x it did work .but I would like to use my voodoo 5 are there any reason some work and some don't, headgear vr isn't hi res. Only256 colors
![[VOD] Revisiting the Palm, a new motherboard, and whatever else I find to do #twitch #vod](/img/0.gif)