Nekonomicon - pub

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Am I toasting my V6? at May 17, 2006, 1:10 p.m...

Hello,
Tired of the poor resolution I had, I've decided to switch to a 1280x1024 mode. After several tries, I managed to set up my V6 to the wanted resolution. Here's the proof :

Code: Select all


   # /usr/gfx/gfxinfo -vvv
   

   Graphics board 0 is "ODYSSEY" graphics.
   

   Managed (":0.0") 1280x1024
   

   BUZZ version A.1
   

   PB&J version 1
   

   32MB memory
   

   Banks: 2, CAS latency: 3
   

   Monitor 0 type: Unknown
   

   Input Sync: Voltage - Video Level; Source - Internal; Genlocked - False
   

   Channel 0:
   

   Origin = (0,0)
   

   Video Output: 1280 pixels, 1024 lines, 59.00Hz (1280x1024_59)
   

   Video Format Flags:  (none)
   

   Sync Disabled
   

   Using Gamma Map 0
   

   Monitor Type:  unknown
   

   Gain (all color components) - 0.000000 ; range [1,10]
   

   #

Oh! I forgot a hinv -vm :

Code: Select all


   # hinv -vm
   

   Location: /hw/node
   

   PM10600MHZ Board: barcode MZL357     part 030-1776-001 rev  B
   

   Location: /hw/node/xtalk/15
   

   IP30 Board: barcode KSC685     part 030-1467-001 rev  D
   

   Location: /hw/node/xtalk/15/pci/2
   

   FP1 Board: barcode KKZ898     part 030-0891-003 rev  G
   

   PWR.SPPLY.ER Board: barcode AAE0460405 part 060-0035-002 rev  A
   

   Location: /hw/node/xtalk/11
   

   ODY32 Board: barcode LEB814     part 030-1403-003 rev  B
   

   1 600 MHZ IP30 Processor
   

   Heart ASIC: Revision F
   

   CPU: MIPS R14000 Processor Chip Revision: 2.4
   

   FPU: MIPS R14010 Floating Point Chip Revision: 0.0
   

   Main memory size: 2048 Mbytes
   

   Xbow ASIC: Revision 1.4
   

   Instruction cache size: 32 Kbytes
   

   Data cache size: 32 Kbytes
   

   Secondary unified instruction/data cache size: 2 Mbytes
   

   Integral SCSI controller 0: Version QL1040B (rev. 2), single ended
   

   Disk drive: unit 1 on SCSI controller 0 (unit 1)
   

   Disk drive: unit 2 on SCSI controller 0 (unit 2)
   

   Disk drive: unit 3 on SCSI controller 0 (unit 3)
   

   Integral SCSI controller 1: Version QL1040B (rev. 2), single ended
   

   IOC3/IOC4 serial port: tty1
   

   IOC3/IOC4 serial port: tty2
   

   IOC3 parallel port: plp1
   

   Graphics board: V6
   

   Integral Fast Ethernet: ef0, version 1, pci 2
   

   Iris Audio Processor: version RAD revision 12.0, number 1
   

   PCI Adapter ID (vendor 0x10a9, device 0x0003) PCI slot 2
   

   PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 0
   

   PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 1
   

   PCI Adapter ID (vendor 0x10a9, device 0x0005) PCI slot 3

I'm a bit upset: when I'm playing a movie with "neko_mplayer", I'm getting the movie window, plus flashing rectangles on the lower half of the screen. And those flashing rectangle also appear when I preview neko_xscreensavers. For both mplayer and xscreensaver, the flashes don't appear when I'm in a fullscreen mode.

The reason why I'm upset is that I read somewhere that there is a frequency bug in the V6/V8, which means that they shoudn't be able to manage a range of frequencies, whose lower bound is about 103 MHz (don't remember about the higher bound). When I launch 'xsetmon', I can see that the Pixel Clock has a value of 107,76 MHz. So do I have to crawl eBay for a new V6?

Thanks in advance for your answers.

PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Am I toasting my V6? at May 17, 2006, 2:58 p.m...

Hello schleusel,

First of all, thanks for your quick answer.

Modes that are close to the lower end of that range (like 1280x1024_59/60) are only allowed at 8 bytes/pixel framebuffer size and even at that setting some people reported display problems (noise, flickering) in other threads

I'm running a 1280x1024_59 mode at 16 bytes/pixel, which shouldn't be possible ?!?

How did you manage to push your V6 to a 1600x1200 resolution ? I'm not allowed to do this in 'xsetmon', in the 'Valid Formats' field :

Code: Select all


   [...]
   

   DX 1280x1024_59
   

   [...]
   

   X 1600x1200_**
   

   [...]

Any trick ?

Thanks,
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Am I toasting my V6? at May 18, 2006, 4:20 a.m...

Hello schleusel,
Thanks for the tip, I'll try it tonight.
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
Who joined Jan. 13, 2006, 10:39 a.m.
and authored 179 notes

Wrote on the subject of Making Irix safe for Internet Banking at Nov. 13, 2006, 11:44 a.m...

Hello indy_tigger,
I'm running IRIX 6.5.27, and I use this box for all my e-banking (I come from Switzerland ;-)

). Maybe I'm a bit naive, but since your transactions are encrypted (ssl, https,...), and you box is secured (the unused ports are close), I don't think you have much to fear, do you?
Of course, as always, if someone really wants to bother you...
Hope this helps,
PB

_________________
Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
Who joined Jan. 13, 2006, 10:39 a.m.
and authored 179 notes

Wrote on the subject of Making Irix safe for Internet Banking at Nov. 14, 2006, 10:09 a.m...

indy_tigger wrote:

Thanks for the replies, I was pretty much convinced before.

I've install ipfilter and I'm going to lock down all the ports apart from http 80 as I don't need them open apart from sharity (what ever ports it uses)

Thanks

And what about https?

PB

_________________
Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
Who joined Jan. 13, 2006, 10:39 a.m.
and authored 179 notes

Wrote on the subject of Making Irix safe for Internet Banking at Nov. 14, 2006, 10:46 a.m...

indy_tigger wrote:

Yep https to, thanks for the heads up.

What start up file would I add the command to load the rule set? can I have them loaded before I get to the visual login so that all the accounts have them?

Some pointers :
http://stuff.mit.edu/afs/sipb/service/i ... STALL.IRIX
http://docs.hp.com/en/B9901-90009/ch01s08.html
http://techpubs.sgi.com/library/tpl/cgi ... 936-PARENT

I would start having a glance at those pages, just to have some good ideas.

Hope this helps,
PB

_________________
Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Commented script to CLONE ROOT DISK at Dec. 18, 2006, 1:20 p.m...

Hello,

I've just got a 73 Go disk from eBay, and I've decided to reorganize my partitions and disks. One of the steps is to clone my actual 18 Go system disk onto this 73 Go. The script of foetz and BetXen will do the job.
The step I've come across were :
- fx to create the partitions on the new /dev/dsk/dks0d2, with the answers given in the first commented part of the script;
- run the script : './diskcloner.sh 0 1 0 2', which complains about 2 inodes at 15%, and an orphan at about 90%;
- power-off the octane.

After having extracted the former system disk, and replaced it with the newly created one (on scsi id 1), I rebooted the computer, and miserably arrived to a "prom" screen saying :

Code: Select all


   Unable to execute xio(0)pci(15)scsi(0)disk(1)rdisk(0) partition(0): execute format error
   

   

   

   

   Autoboot failed
   

   xio(0)pci(15)scsi(0)disk(1)rdisk(0) partition(0): execute format error
   

   Hit Enter to contine

Nice... Could it mean that the drive I've just bought on eBay is crappy, or did I do something wrong?

Thanks in advance for any advise/answer.

PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Commented script to CLONE ROOT DISK at Dec. 18, 2006, 2:56 p.m...

Hello,

joerg wrote: You can create the missing info within the fx tool.

Is it too late for me to do that by now, after having already copied the other partitions with the script?

And is it related to the 'OSLoadFilename' variable Ian Mapleson is talking about in http://futuretech.blinkenlights.nl/disksfiles.html#CLONE , in the 'Cloning A Root Disk' section?

porter wrote: (a) fx to setup the disk
(b) xfsdump/xfsrestore to save restore contents
(c) dvhtool to update the volume header with new sash.

If I can't have the script work for my case, I'll have to try that way. Thanks for the tip!

PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Commented script to CLONE ROOT DISK at Dec. 29, 2006, 11:54 a.m...

Hello,
Thanks for your help. I managed to boot from this newly cloned drive simply by adding

Code: Select all


   setenv OSLoadFilename /unix

in the 'PROM shell'.

As a contribution, I'd like to propose a patch to this so useful script: with a small change, it can be used to clone option disks as well:

Code: Select all


   --- diskcloner.sh.orig  Fri Dec 29 19:28:15 CET 2006
   

   +++ diskcloner.sh       Fri Dec 29 20:38:58 CET 2006
   

   @@ -66,6 +66,9 @@
   

   export target_cntrl=$3
   

   export target_drv=$4
   

   

   +export system_mode="System"
   

   +export option_mode="Option"
   

   +
   

   clear
   

   

   if [[ $# != 4 ]]; then
   

   @@ -91,88 +94,108 @@
   

   exit 1
   

   

   else
   

   -   print ""
   

   -   print "***************************"
   

   -   print "* ... formatting disk ... *"
   

   -   print "***************************"
   

   -   print ""
   

   -   mkfs /dev/rdsk/dks${target_cntrl}d${target_drv}s0
   

   +   select mode in $system_mode $option_mode Exit; do
   

   +      if [[ "$mode" = "$system_mode" || "$mode" = "$option_mode" ]] ; then
   

   +         break;
   

   +      elif [[ "$mode" = "Exit" ]] ; then
   

   +            exit 1;
   

   +      fi
   

   +         print "Wrong choice... Hit a digit!";
   

   +   done
   

   +fi
   

   -   print ""
   

   -   print "*************************"
   

   -   print "* ... mounting disk ... *"
   

   -   print "*************************"
   

   -   print ""
   

   -   mkdir /sgi_clone_dsk_tmp
   

   -   mount /dev/dsk/dks${target_cntrl}d${target_drv}s0 /sgi_clone_dsk_tmp
   

   +if [[ "$mode" = "$system_mode" ]] ; then
   

   +       export target_partition=0;
   

   +elif [[ "$mode" = "$option_mode" ]] ; then
   

   +       export target_partition=7;
   

   +else
   

   +       print "This shouldn't have happened! Exiting...";
   

   +       exit 1;
   

   +fi
   

   

   +print ""
   

   +print "***************************"
   

   +print "* ... formatting disk ... *"
   

   +print "***************************"
   

   +print ""
   

   +mkfs /dev/rdsk/dks${target_cntrl}d${target_drv}s${target_partition}
   

   +
   

   +print ""
   

   +print "*************************"
   

   +print "* ... mounting disk ... *"
   

   +print "*************************"
   

   +print ""
   

   +mkdir /sgi_clone_dsk_tmp
   

   +mount /dev/dsk/dks${target_cntrl}d${target_drv}s${target_partition} /sgi_clone_dsk_tmp
   

   +
   

   #  Uncomment the next lines if you want the script to inform you about available
   

   #  space on the destination disk. Would take time, but could be usefull if you
   

   #  have a smaller disk.
   

   #
   

   -#   print ""
   

   -#   print "***********************************************************"
   

   -#   print "* ... giving size infos (in terms of 1024-byte blocks)... *"
   

   -#   print "***********************************************************"
   

   -#   print ""
   

   -#   print "Disk usage of /:"
   

   -#   du -k -s /
   

   -#   print ""
   

   -#   print "Free space on target disk:"
   

   -#   df -k /dev/dsk/dks${target_cntrl}d${target_drv}s0
   

   -#   print ""
   

   -#   print "     PLEASE CHECK SPACE!"
   

   -#   print "     Sleeping 15 seconds to let you abort script..."
   

   -#   sleep 15
   

   -
   

   -   print ""
   

   -   print "************************************"
   

   -   print "* ... duplicating data content ... *"
   

   -   print "************************************"
   

   -   print ""
   

   -   print "Informations will be given every 30 seconds."
   

   -   print ""
   

   -   cd /sgi_clone_dsk_tmp
   

   +#print ""
   

   +#print "***********************************************************"
   

   +#print "* ... giving size infos (in terms of 1024-byte blocks)... *"
   

   +#print "***********************************************************"
   

   +#print ""
   

   +#print "Disk usage of /:"
   

   +#du -k -s /
   

   +#print ""
   

   +#print "Free space on target disk:"
   

   +#df -k /dev/dsk/dks${target_cntrl}d${target_drv}s${target_partition}
   

   +#print ""
   

   +#print "     PLEASE CHECK SPACE!"
   

   +#print "     Sleeping 15 seconds to let you abort script..."
   

   +#sleep 15
   

   +
   

   +print ""
   

   +print "************************************"
   

   +print "* ... duplicating data content ... *"
   

   +print "************************************"
   

   +print ""
   

   +print "Informations will be given every 30 seconds."
   

   +print ""
   

   +cd /sgi_clone_dsk_tmp
   

   #  If you don't want infos during the process, remove "-p 30" in the next line.-   timex xfsdump -l 0 -p 30 - / | xfsrestore - .
   

   +timex xfsdump -l 0 -p 30 - / | xfsrestore - .
   

   

   -   print ""
   

   -   print "*****************************"
   

   -   print "* ... making boot stuff ... *"
   

   -   print "*****************************"
   

   -   print ""
   

   -   cd /stand
   

   -   dvhtool -v get sash sash /dev/rdsk/dks${orig_cntrl}d${orig_drv}vh
   

   -   dvhtool -v get ide ide /dev/rdsk/dks${orig_cntrl}d${orig_drv}vh
   

   -   dvhtool -v creat sash sash /dev/rdsk/dks${target_cntrl}d${target_drv}vh
   

   -   dvhtool -v creat ide ide /dev/rdsk/dks${target_cntrl}d${target_drv}vh
   

   +if [[ "$mode" = "$system_mode" ]] ; then
   

   +       print ""
   

   +       print "*****************************"
   

   +       print "* ... making boot stuff ... *"
   

   +       print "*****************************"
   

   +       print ""
   

   +       cd /stand
   

   +       dvhtool -v get sash sash /dev/rdsk/dks${orig_cntrl}d${orig_drv}vh
   

   +       dvhtool -v get ide ide /dev/rdsk/dks${orig_cntrl}d${orig_drv}vh
   

   +       dvhtool -v creat sash sash /dev/rdsk/dks${target_cntrl}d${target_drv}vh
   

   +       dvhtool -v creat ide ide /dev/rdsk/dks${target_cntrl}d${target_drv}vh
   

   +fi
   

   

   #  Uncomment the next lines if you plan to use this script as a backup one and
   

   #  to write a file containing the date and time on your disks' root folder.
   

   -#   print ""
   

   -#   print "***************************************************"
   

   -#   print "* ... writing /_LAST_CLONE_.txt on both disks ... *"
   

   -#   print "***************************************************"
   

   -#   print ""
   

   -#   echo "Last clone using sgi_clone_disk script made on " > /_LAST_CLONE_.txt
   

   -#   date >> /_LAST_CLONE_.txt
   

   -#   more /_LAST_CLONE_.txt > /sgi_clone_dsk_tmp/_LAST_CLONE_.txt
   

   -
   

   -   print ""
   

   -   print "**********************"
   

   -   print "* ... unmounting ... *"
   

   -   print "**********************"
   

   -   print ""
   

   -   cd /
   

   -   umount /sgi_clone_dsk_tmp
   

   -   sleep 10
   

   -   rm -rf /sgi_clone_dsk_tmp
   

   -
   

   -   print ""
   

   -   print "****************"
   

   -   print "* ... done ... *"
   

   -   print "****************"
   

   -   print ""
   

   +#print ""
   

   +#print "***************************************************"
   

   +#print "* ... writing /_LAST_CLONE_.txt on both disks ... *"
   

   +#print "***************************************************"
   

   +#print ""
   

   +#echo "Last clone using sgi_clone_disk script made on " > /_LAST_CLONE_.txt
   

   +#date >> /_LAST_CLONE_.txt
   

   +#more /_LAST_CLONE_.txt > /sgi_clone_dsk_tmp/_LAST_CLONE_.txt
   

   +
   

   +print ""
   

   +print "**********************"
   

   +print "* ... unmounting ... *"
   

   +print "**********************"
   

   +print ""
   

   +cd /
   

   +umount /sgi_clone_dsk_tmp
   

   +sleep 10
   

   +rm -rf /sgi_clone_dsk_tmp
   

   +
   

   +print ""
   

   +print "****************"
   

   +print "* ... done ... *"
   

   +print "****************"
   

   +print ""
   

   

   -fi
   

   exit 0

Any modification/correction/enhancement is of course welcome!

HTH,
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Commented script to CLONE ROOT DISK at Dec. 29, 2006, 4:11 p.m...

Hello joerg,
Adding this info into the bootinfo can be done with fx, can't it?
Actually, when I run fx on (ctlr = #0, drive = #1, lun = #0), '[l]abel' => '[s]how' => '[b]ootinfo', I only see:

Code: Select all


   ----- bootinfo-----
   

   root partition = 0     swap partition = 1    bootfile =

As I'm a bit stressed by doing something wrong here, causing potential unvolontary disk erasure, could you explain me which steps you go through to set up the 'bootfile' field?
Thanks in advance,
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Commented script to CLONE ROOT DISK at Dec. 29, 2006, 4:46 p.m...

Code: Select all


   ----- bootinfo-----
   

   root partition = 0     swap partition = 1    bootfile = /unix

It worked! Thank you for the tip!
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Nekoware-current at Jan. 21, 2007, 10:11 a.m...

You're welcome, and thank you for the tip!
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Nekoware-current at Jan. 22, 2007, 3:23 a.m...

ant_39 wrote: Yay, links! I love this browser, actually used it for quite a while exclusively. It's good to have it or irix!
As for the packaging, I miss spec and idb files. They usually come in "distribution files" folder I think. Being quite new in packaging, I'll welcome corrections, but this seems to be implied by Packaging_Software wiki page.

Really ? Ok, I'll give it a look tonight, and upload the corrected version.
Thanks for the feedback!
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Nekoware-current at Jan. 22, 2007, 9:54 a.m...

pub_bronx wrote:

ant_39 wrote: Yay, links! I love this browser, actually used it for quite a while exclusively. It's good to have it or irix!
As for the packaging, I miss spec and idb files. They usually come in "distribution files" folder I think. Being quite new in packaging, I'll welcome corrections, but this seems to be implied by Packaging_Software wiki page.

Really ? Ok, I'll give it a look tonight, and upload the corrected version.
Thanks for the feedback!
PB

Oups, you were right! I'm currently uploading a new archive. To clarify the difference with the previous one, I've introduced a tardist release number ( -1 in this current case). OK with that (this is related to this page ) ?
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of fun with network install onto clean disk at July 7, 2007, 4:34 a.m...

thermionic wrote: FreeBSD rshd is now working with inst It needed several changes to /etc/pam.d/rsh to get it "open" enough.

Then a quick change of sh to ksh and inst can see the distributions, YAY !

Hi Thermionic,
I guess that you've once found a solution to my actual problem ... Could you please tell me more about the changes you've applied to rsh and/or rshd to have a network installation from FreeBSD work ?
Thanks in advance,
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of fun with network install onto clean disk at July 7, 2007, 9:03 a.m...

josehill wrote: Now that's starting to sound like a wiki article!

As soon as I've managed to net install my box, I'll publish my experiences on this subject in the wiki. But for now...
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of fun with network install onto clean disk at July 10, 2007, 1:18 a.m...

thermionic wrote: (little to drunk to do it now)

Hello Thermionic,
Thank you very much, but I think I've solved my problem (see this post ).
In the next few days, I'll post an article in the wiki, to explain all the steps one have to perform to net-install a box. My contribution will be about installation from FreeBSD. Other people may add contributions about installation from other systems.
Your posts in this thread have helped me a lot. Thanks again.
Regards,
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of fun with network install onto clean disk at July 15, 2007, 7:42 a.m...

Hello,
Wiki article about net-installing an Octane from a FreeBSD box added here !
HTH,
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of fun with network install onto clean disk at July 15, 2007, 8:19 a.m...

LoWeN wrote: Hello,

You can also add to your wiki article that this is also valid for FreeBSD 6.2.

@+

LoWeN

Hello LoWen,
Updated ! Thanks for the information.
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of fun with network install onto clean disk at July 20, 2007, 1:37 p.m...

Wiki updated (at the bottom...). Thank you, LoWeN!
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Needed hardware to digitalize VHS tapes ? at Sept. 14, 2008, 1:29 a.m...

Hello,

I'm planning to digitalize some old VHS tapes, and I'm looking for the cheapest way to do it. In my computer "stock", I have the following items:

Octane R14k 600Mhz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

O2 195MHz (IIRC it has not a lot of RAM, and nothing related to video)

Indigo2 (don't remember either, since it hasn't been fire up since a long time)

Mac Pro 2x2.8GHz Quad-Xeon, 2GB RAM

Standard old PC
What do you think I need to be able to transfer my old VHS movies to something viewable on a DVD ?

Thanks in advance for any advise !

PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

pub_bronx
From Switzerland
Who joined Jan. 13, 2006, 10:39 a.m.

Wrote on the subject of Needed hardware to digitalize VHS tapes ? at Sept. 26, 2008, 11:21 a.m...

Hello,
Thanks for your replies!
PB

Octane R14k 600MHz, V6, 2048 MB RAM, 73GB HD0, 18GB HD1, 73GB HD2

The collected works of pub_bronx