This is Nosubject in view mode; [Up]
Date: Sun 17-Apr-1991 09:23:24 From: mark@epsoft.UUCP (Mark Chamberlain) Subject: Re: Gary Lang writes -> >> I've recently built up a fairly decent ATM library of fonts under >> Windows 3. Now these are all Adobe Type 1 fonts - how can I use >them >> on my NeXT? I have a set of files with pfb and pfm extensions - how >> do I build these into .font files? >> >> TIA, Mark >> ---- >> Mark Chamberlain, Epsilon Software Limited, London, England >> uunet!ukc!epsoft!mark > >For starters buy a copy form Adobe; it's illegal for you to use them >on your >Windows AND NeXT machines. Pay for the software you use please. There are a *great* deal of PD/Shareware Type 1 fonts, and those are the ones I have. ---- Mark Chamberlain, Epsilon Software Limited, London, England uunet!ukc!epsoft!mark
Date: Sun 22-Apr-1991 19:14:46 From: scoezec@hpuxa.acs.ohio-state.edu (Mark D. LeScoezec) Subject: (none) Has anybody had any luck getting perl4.0 to work? Please send me any information. mark lescoezec mark@tampa.ovl.osc.edu
Date: Sun 06-May-1991 20:19:59 From: cnh5730@maraba.tamu.edu (Charles Herrick) Subject: Re: (I sure do ask a lot of questions) In article <1991May6.022520.12409@athena.mit.edu> isbell@athena.mit.edu (Charles L Isbell) writes: Say, anyone out there know where I can get any info on the TIFF (or hey the GIF) format? yes. oh, OK. subscribe to comp.graphics.
Date: Sun 14-May-1991 00:08:52 From: carlos@roo (Carlos M. Salinas) Subject: Re: (I sure do ask a lot of questions) > In article <1991May6.022520.12409@athena.mit.edu> isbell@athena.mit.edu (Charles L Isbell) writes: > Say, anyone out there know where I can get any info on the > TIFF (or hey the GIF) format? > A doc on the tiff format was included in the .8 and .9 doc set. 'Los
Date: Sun 23-May-1991 08:44:36 From: izumi@mindseye.berkeley.edu (Izumi Ohzawa) Subject: (Updated) Fujitsu SCSI disk installation note (LONG) *** Installing FUJITSU M2263SA/SB SCSI Disk as NeXT Boot Disk [Doc Version 2.1, May 20, 1991] Izumi Ohzawa, izumi@violet.berkeley.edu (standard mail) izumi@pinoko.berkeley.edu (NeXTmail) This note was originally posted to a USENET newsgroup comp.sys.next sometime during the summer 1990. Updates have been made to include notes for OS Release 2.0/2.1. With the exception of disk capacity related numbers, procedures described below should also apply to M2261SA/SB, and M2266SA/SB (1.2GB) drives. Short descriptions are presented first for using the drive as (1) internal boot disk in a NeXTcube, and (2) external boot disk for NeXTstation/cubes. Long descriptions follow these. ========================================================================== (1) *** Installing M2263Sx as Internal Boot Disk for NeXTcube. [For Release 2.0/2.1] I assume here that the cube can boot from the optical disk drive, or from ethernet. If your cube cannot boot from either of these, you will have to use another NeXT machine to make your new disk bootable. [I1] Set the SCSI ID (target#) of the new drive to 1 on CN9. Remove jumpers at both ends of CNH2 (see step [1]). For internal disk, the SCSI terminator should be left installed. (20-pin DIP resister module next to the SCSI connector on the drive) [I2] Install the drive in the NeXTcube above the optical drive. [I3] Power up the NeXT machine, boot from OD or Ethernet. [I4] Login as root. [I5] scsimodes /dev/rsd0a should show the drive parameters of the Fujitsu drive (see step [3] below). [I6] If you feel adventurous, do low-level formatting using 'formatter'. You generally do not have to perform any low-level format. Choose the correct SCSI ID, i.e., 1, and press format button. (or use NeXT-supplied sdform program: /usr/etc/sdform /dev/rsd0a). (See step [3.5] below for details). [I7] From Terminal, do /usr/etc/builddisk sd0 Wait upto an hour for full disk build. [I8] Install boot block. /usr/etc/disk -b /dev/rsd0a [I9] Mount the newly built disk. Edit etc/fstab on the new disk to remove/comment out the line for /dev/sd0b (client partition). Unmount the disk. [I10] Reboot from the new scsi disk, e.g., in Terminal, halt bsd ========================================================================== (2) *** Installing M2263Sx as External Boot Disk for NeXTstaion/cube. [For Release 2.0/2.1] ** Warning ** I have not tested this procedure. It should work, but no guarantees. Assumption here is that you have a friend who has a 2.0/2.1 Extended system, and she will let you connect your new drive to her machine and load the system onto your drive. In this case, you will be making the new external drive the boot disk of your system. The internal disk that came with the computer will become a secondary disk. You should still be able to use the machine without the external disk, if you keep the minimum configuration intact. If your machine boots from the internal drive, and you are just adding a non-boot disk externally, you don't probably have to do anything under 2.0/2.1 other than setting the jumpers (step [E1] below). [E1] Set the SCSI ID (target#) of the new external drive to 2 on CN9. Remove jumpers at both ends of CNH2 (see step [1]). If this disk is the only or last device on the external SCSI bus, leave the terminator ON (20-pin DIP resister module next to the SCSI connector on the drive). If the disk is in the middle of the SCSI chain, remove the terminator. [E2] Connect the drive to SCSI port of the main unit (with powers off). [E3] Power up the external drive, and then the NeXT machine. [E4] Login as root. [E5] scsimodes /dev/rsd1a This should show the drive parameters of the Fujitsu drive. (see step [3] below). Make DAMN sure that you specify /dev/rsd1a, and that you get "FUJITSU ..." message in the output. Otherwise, you might wipe out your friend's disk accidentally. [E6] If you feel adventurous, do low-level formatting using 'formatter'. You generally do not have to perform any low-level format. Choose the correct SCSI ID, i.e., 2, and press format button. (or use NeXT-supplied sdform program: /usr/etc/sdform /dev/rsd1a). (See step [3.5] below for details). [E7] From terminal, do /usr/etc/builddisk sd1 Wait upto an hour for full disk build. [E8] Install boot block. /usr/etc/disk -b /dev/rsd1a [I9] Mount the newly built disk. Edit etc/fstab on the new disk to remove/comment out the line for /dev/sd0b (client partition). Unmount the disk and power down the NeXT and the external disk. [E10] Change the SCSI ID (target#) of the drive to 0. Take the drive home, and connect to your NeXT. Your NeXT should now boot from the new external drive. (The external drive is now /dev/sd0a, and the internal /dev/sd1a.) [E11] Edit /etc/fstab to add a line to mount the internal drive. /dev/sd1a /Internal 4.3 rw,noquota 0 2 Of course, you can replace "Internal" with any name you desire as the directory at which the internal drive is mounted. [E12] Reboot. [E13] Clean-up the internal drive, if you want to make space by deleting non-essential stuff that is duplicated on the external drive. ========================================================================== This is the long version of the installation note. Descriptions primarily apply to the case where the drive is mounted internally in the NeXTcube. Please make necessary corrections or disregard irrelevant descriptions if your drive is externally mounted, e.g., changing rsd0a to rsd1a where necessary. [0] I assume you know how to handle electro-static sensitive devices. If you don't, read Appendix C "Opening the Cube" of User's Reference which you should have received with your cube. [1] Jumper settings on the drive (a) SCSI target# can be set by jumber block "CN9" located right next to the SCSI bus connector of the drive. Three jumpers closest to the SCSI connector encode the target number in binary. View from the back of the drive, with the drive UP-SIDE DOWN. |-----------| |----------------------------| ....... | power con.| | 50 pin SCSI connector | CN9 ....... |-----------| |----------------------------| \-/ ID For SCSI target# 0, remove the three left-most jumpers on CN9. For SCSI target# 1, keep the left-most one, and remove the second and third jumper from left. Figure out other target ID's yourself using the left-most jumber as LSB (least significant bit). The recommended target# for internal boot disk is 1. This allows an external SCSI drive with target #0 to become the boot device when such a device is connected (without opening the cube). (The cube will boot from the SCSI device with the smallest target #. Manual booting from the ROM monitor will always allow booting from a SCSI device with any target #.) (b) Remove two jumpers at both ends of the jumper block "CNH2". Locate the jumper block "CNH2" betweeen two surface-mount VSLI's whose labels are obscured by capacitors ( 1cm square blocks colored blue on my drive, with two leads). There are 8 jumpers in this block. On Jumper Block "CNH2" remove: [1-2] INQUIRY DATA [15-16] Synchronous Mode Transfer If you can't figure out the numbers on the block, [1-2] is at one end and indicated by a little triangle mark, and [15-16] is at the other end (8-th position from the triangle). Both of the jumbers in CNH2 have to be pulled out for 68030 (old cube), 68040 CPU boards, and NeXTstation. (See attached comp.sys.next article at the end.) [ This information was kindly provided by Helene Young-Myers, helene@secd.cs.umd.edu, and her husband Eugene D. Myers. ] You will be able to perform BuildDisk with these two jumpers on, and will be able to mount and use the drive if it is not used as the boot disk. However, the cube will not boot when you try to boot from the new SCSI drive later in step [8]. These two jumpers are probably the only ones you have to change from the factory configuration. On my drive, all other jumpers in block "CNH2" are installed except for the two above. All jumpers in block "CNH1" and "CNH4" are also on. (c) SCSI Terminator If you are installing the drive inside the cube, leave the terminator on (20-pin DIP resister module next to the SCSI connector on the drive). If this disk is the only or last device on the external SCSI bus, leave the terminator ON. If the disk is in the middle of the SCSI chain, remove the terminator. [2] Remove the 40MB swap disk if present, and install M2263S. Connect the power cable to the drive, and SCSI flat cable. Make sure that pins (50 each on the SCSI drive, and the CPU board) are not bent. Straighten them if any are bent. If you are using an internal SCSI cable from a third-party vendor, use caution not to insert the connector upside-down. The NeXT supplied internal SCSI cable is keyed, so it shouldn't be possible to insert it upside-down. If, in step [3], "scsimodes" does not give you anything other than error messages, you might have connected the cable in the wrong way. There is a little label on the connector of the drive indicating which pin is pin-1. Make sure that the same side of the cable goes to pin-1 on the drive and the CPU board. [3] Boot from OD, and login as user "root". Use command "scsimodes" as below to get basic formatting information, e.g., bytes per sector, etc. If "scsimodes" does not work, the most likely cause is improper cable connections. --- For M2263SA localhost# scsimodes /dev/rsd0a (/dev/rsd1a if external) SCSI information for /dev/rsd0a Drive type: FUJITSU M2263S-512 512 bytes per sector 53 sectors per track 15 tracks per cylinder 1658 cylinder per volume (including spare cylinders) 3 spare sectors per cylinder 15 alternate tracks per volume 1312343 usable sectors on volume --- For M2263SB (or SA after running "formatter") localhost# scsimodes /dev/rsd0a (/dev/rsd1a if external) SCSI information for /dev/rsd0a Drive type: FUJITSU M2263S-1024 1024 bytes per sector 28 sectors per track 15 tracks per cylinder 1658 cylinder per volume (including spare cylinders) 3 spare sectors per cylinder 15 alternate tracks per volume 690968 usable sectors on volume [3.5] Low-level Formatting (*** OPTIONAL ***) If you have a program "formatter" by Rory Bolt (see below), you can optionally perform a low-level format of M2263SA. You can also use a NeXT supplied program /usr/etc/sdform for this purpose although it cannot do many of the things "formatter" can. Rory's program has been written specifically for Fujitsu M226xS series drives although it works with many other SCSI drives. Your drive should work without this step, however. Therefore, skip it if you are unconfortable doing it. Low-level formatting is not really required because the drive comes pre-formatted from factory. However, running "formatter" will give you additional 35MB of storage from M2263SA by essentially turning it into an M2263SB, speeds up the drive slightly, and it will enable automatic error recovery feature of the Fujitsu drive. [You get about 632MB for M2263SA, and 667MB for M2263SB after i-nodes and other Unix overhead are subtracted. The difference between SA and SB is that SA has 512 bytes/sector block size while SB has 1024 bytes/sector. If you can get M2263SB instead of SA from a vendor, by all means get the SB version.] Also, remember for future reference that there are certain SCSI disk errors which can usually be fixed by low-level formatting a drive. If your drive, after some use, develops "MEDIA ERRORs" which will be recorded in the system log file /usr/adm/messages, you might be able to fix the drive by doing a low-level format. These media errors cannot be fixed by simply re-doing BuildDisk and reloading the system. If a low-level format doesn't revive the disk, it's time to ship the disk back to the manufacturer. Low-level formatting is different from the intialization process performed by BuildDisk or by command line "disk -i /dev/rsd0a". The init process done by BuildDisk or disk program merely lays down Unix filesystem(s), while a low-level format freshens formatting and bad-sector substitution table internal to the SCSI disk. The low-level formatting process will take 20-30 minutes for 670MB drive, while the BuildDisk init process (or "disk -i /dev/rsd0a") will take only a few minutes. **** How to get "formatter" (v1.2) by Rory Bolt. This program is available from the standard NeXT archive sites via anonymous FTP if you are connected to Internet. If you do not have FTP access, Purdue University archive also operates an E-mail based file server. This is a shareware program ($15), so please send a check to Rory if the program works for you. (Once is all you need to run this program, usually. It is also a better deal than the other program TheFormatter for Wren's.) [I have no connection with Rory Bolt except as a happy user of his program.] The current version (1.2) was develped on NeXT OS 1.0, but works fine on Release 2.0 too [I've done it.] NeXT FTP archives are as follows: To obtain formatter_1.2.tar.Z via E-mail based file server: Send mail to: archive-server@cc.purdue.edu with the subject line, [ ^-- Not a typo. SPACE here.] Body of the message can be empty. You will receive the file uuencoded. Size of the program after uuencoding is about 34kbytes, thus there shouldn't be any problem for it to go through various gateways. If you have trouble with the e-mail server, or want to obtain further information on the Purdue e-mail archive server, send mail to the same address with, If you cannot obtain "formatter" from these sites, you can still perform low-level format with a NeXT supplied program "sdform". However, "sdform" cannot change the block size from 512 to 1024 bytes/sector, and therefore cannot increase the capacity for M2263SA. For locking out bad sectors, "sdform" should be satisfactory. Use "sdform" as follows (as user "root"): localhost# /usr/etc/sdform /dev/rsd0a (/dev/rsd1a if external) (This also takes 20-30 minutes. Do not interrupt once started.) ###### Release 2.0/2.1 Note ################################################ Skip steps [4] and [5] if you have OS Release 2.0/2.1, and want to use the whole disk as one partition. No modification to /etc/disktab is needed. Steps [4] and [5] are relevant only if one the following applies: (a) Your OS release is still 1.0 or 1.0a. (b) OS is 2.0/2.1, but you need multiple partitions on the disk.
[4] Add the following entry to the end of "/etc/disktab". [Not requried for OS Release 2.0/2.1] If the parameters shown by "scsimodes" are different from those above, you cannot use the entry below. If you want the modified disktab to appear also in the SCSI disk's /etc/disktab after BuildDisk, copy /etc/disktab to /usr/template/client/etc/disktab, too. ( BuildDisk will copy /usr/template/client/etc/* onto a newly built disk as /private/etc/* ) Be sure to make backup copies of the unmodified disktab in each directory. Write permission may have to be set to edit these files. ----- cut here and append to /etc/disktab ----------------------------------- # FUJITSU M2263SA disktab # FUJITSU M2263S-512 with 3 spare sectors/cylinder and 512 byte sectors # localhost# scsimodes /dev/rsd0a # SCSI information for /dev/rsd0a # Drive type: FUJITSU M2263S-512 # 512 bytes per sector # 53 sectors per track # 15 tracks per cylinder # 1658 cylinder per volume (including spare cylinders) # 3 spare sectors per cylinder # 15 alternate tracks per volume # 1312343 usable sectors on volume # # This disktab entry from: majka@cs.ubc.ca (Marc Majka) # Organization: UBC Department of Computer Science, Vancouver, B.C., Canada # Fujitsu M2263S 671MB 5.25" drive with 512 byte sectors # M2263S - One partition M2263S-512-ALL|Fujitsu 671MB w/512 byte sectors as 1 partition:\ :ty=fixed_rw_scsi:nc#1658:nt#15:ns#53:ss#1024:rm#3600:\ :fp#160:bp#0:ng#0:gs#0:ga#0:ao#0:\ :os=sdmach:z0#32:z1#96:ro=a:\ :pa#0:sa#655875:ba#8192:fa#1024:ca#32:da#4096:ra#10:oa=time:\ :ia:ta=4.3BSD: # M2263S - Two partitions M2263S-512|FUJITSU M2263S-512|Fujitsu 671MB w/512 byte sectors:\ :ty=fixed_rw_scsi:nc#1658:nt#15:ns#53:ss#1024:rm#3600:\ :fp#160:bp#0:ng#0:gs#0:ga#0:ao#0:\ :os=sdmach:z0#32:z1#96:ro=a:\ :pa#0:sa#250425:ba#8192:fa#1024:ca#32:da#4096:ra#10:oa=time:\ :ia:ta=4.3BSD:\ :pb#250425:sb#405450:bb#8192:fb#1024:cb#32:db#8192:rb#10:ob=time:\ :ib:tb=4.3BSD: # # FUJITSU M2263SB disktab, or for M2263Sx after running "formatter". # localhost# scsimodes /dev/rsd0a # SCSI information for /dev/rsd0a # Drive type: FUJITSU M2263S-1024 # 1024 bytes per sector # 28 sectors per track # 15 tracks per cylinder # 1658 cylinder per volume (including spare cylinders) # 3 spare sectors per cylinder # 15 alternate tracks per volume # 690968 usable sectors on volume # # Generated by "formatter v1.2" by Rory Bolt after low-level formatting. # FUJITSU M2263S-1024 M2263S-1024|FUJITSU M2263S-1024|FUJITSU M2263S-1024 w/1024 byte sectors as 1 partition:\ :ty=fixed_rw_scsi:nc#1658:nt#15:ns#28:ss#1024:rm#3600:\ :fp#160:bp#0:ng#0:gs#0:ga#0:ao#0:\ :os=sdmach:z0#32:z1#96:r0=a:\ :pa#0:sa#690809:ba#8192:fa#1024:ca#32:da#4096:ra#10:oa=time:\ :ia:ta=4.3BSD: # ------ cut here --- end of disktab for M2263S -------------------------------- [5] Check if the modified /etc/disktab is valid by; [Not requried for OS Release 2.0/2.1] localhost# disk /dev/rsd0a disk name: FUJITSU M2263S-512 (or -1024) disk type: fixed_rw_scsi Disk utility disk> quit (quit this program) localhost# If the "disk" command does not recognize the drive, you have made a mistake in adding the disktab entry in step [4]. Check /etc/disktab again. [6] Launch "BuildDisk", select HARD DISK and run it. This takes upto one hour. If, for some reason, BuildDisk app does not work, try the command line version from Terminal. [This happened to me once. Since then, I am using the command line version below exclusively.] localhost# builddisk sd0 (sd1 if external) This command is a shell script. Look at /usr/etc/builddisk if you want to find out exactly what it does. You can also give a customized /etc/BLD.* script as an option to this command. [6.5] Install boot block to the disk. localhost# disk -b /dev/rsd0a (/dev/rsd1a if external) Apparently, BuildDisk (or command line builddisk) does not write the 2.0 boot block to the disk. The boot block is needed to load the Mach kernel into memory as a first step in booting the machine. The boot block does not exist if you have done a low-level format, or if you have just received the drive from a dealer. [7] If you are using the first disktab entry (the whole disk as one large partition) or if you didn't put a disktab entry because your OS is 2.0/2.1, you must edit "/etc/fstab" on the SCSI disk before you attempt to boot from it. After builddisk, "/etc/fstab" for some reason contains 2 partitions "sd0a", and "sd0b", the latter of which of course does not exist. Because of this, booting will fail and the system will come up in single-user mode in a dumb console window. If you are using the second entry (for two partions), you don't have to modify /etc/fstab. So, skip this step. mount /dev/sd0a /mnt chmod 644 /mnt/etc/fstab Using your favorite text editor, edit /mnt/etc/fstab, and comment out or remove the line: /dev/sd0b /clients 4.3 rw,noquota 0 2 Save the file, and umount /dev/sd0a [8] Shutdown and boot from the SCSI disk. Type 'halt', and you will be left in the ROM Monitor. Type 'bsd' at the ROM Monitor prompt. If the ROM monitor complains: SCSI unexpeced msg:1 sc: Unexpected msg .... repeated many times... Then, you must have not set the jumpers correctly in step [1](b). Once you confirm that the new disk is working, change the default boot device to hard disk using Preferences app (Power button panel). =========================================================================== Additional information of interest [9] Transfer Rate (This was done with 68030 cube under OS Release 1.0a. BEFORE low-level format by Rory Bolt's "formatter.") localhost# disk /dev/rsd0a disk name: FUJITSU M2263S-512 disk type: fixed_rw_scsi Disk utility disk> read starting block? 0 # sectors per transfer? 16 number of transfers? 1000 sector increment? 16 16384000 bytes in 21243 ms = 771374 bytes/s disk> read starting block? 0 # sectors per transfer? 16 number of transfers? 1000 sector increment? 16 16384000 bytes in 21242 ms = 771374 bytes/s For comparison, according to Ronald Antony & Axel Merk (the authors of "TheFormatter" for Wren drives), CDC Wren VI (CDC 94191-15) gives 520000 - 560000 bytes/sec for 512 bytes/sector drive without cache, and 900000 - 980000 bytes/sec with on-drive cache. [10] Seek Noise The Fujitsu drive is quite a bit noisy during seeks. It's not as bad as the OD drive as I said in the old note. You will certainly hear seek noise every time you receive a mail, when a File Viewer opens a directory or when someone does an rlogin, etc. By comparison, Maxtor XT-8760S, the NeXT's official 660MB drive, is dead quiet. Perhaps, the drive may not be suitable if you need a really quiet environment. But the 5-year manufacturer warranty is, for me, quite soothing :-) I don't know how Fujitsu compares with CDC Wren drives with respect to seek noise. [11] As always, use the information above at your own risk. I am not responsible for any damage to the SCSI drive or to the NeXT cube itself (voiding the warranty) caused directly or indirectly by the use of the information provided above. ========================================================================== ATTACHMENT Article 15834 (9 more) in comp.sys.next:
Date: Sun 23-May-1991 15:12:52 From: cnh5730@calvin.tamu.edu (Charles Herrick) Subject: Re: (Updated) Fujitsu SCSI disk installation note (LONG) Am I alone in thinking that Izumi's post should be in the NeXTFAQ.
Date: Sun 23-May-1991 17:19:10 From: fletcher@socrates.umd.edu (Charles Fletcher) Subject: Re: (Updated) Fujitsu SCSI disk installation note (LONG) In article <CNH5730.91May23101252@calvin.tamu.edu> cnh5730@calvin.tamu.edu (Charles Herrick) writes: >Am I alone in thinking that >Izumi's post should be in the NeXTFAQ. >-- > The opinions expressed herein are mine and are in no way attributed > to any of the many people for whom I work. Who they are is irrelevant. I vote YES--my drive arrives tomorrow, so I'll be putting these instructions to the test this weekend. Charlie
Date: Sun 23-May-1991 18:29:01 From: jcargill@oka.cs.wisc.edu (Jon Cargille) Subject: Re: (Updated) Fujitsu SCSI disk installation note (LONG) In <CNH5730.91May23101252@calvin.tamu.edu> cnh5730@calvin.tamu.edu (Charles Herrick) writes: >Am I alone in thinking that >Izumi's post should be in the NeXTFAQ. Actually, in the interest of keeping the FAQ down to a reasonable size, I think it might be more appropriate to put long informational pieces like Izumi's post and the modem instructions in the archives under the 'lore' directory. To make it easy for new people to find these, we could put the question in the FAQ, and answer it with a pointer to the appropriate file in the archives. Jon
Date: Sun 26-May-1991 00:39:46 From: garnett@cs.utexas.edu (John William Garnett) Subject: Re: (Updated) Fujitsu SCSI disk installation note (LONG) In article <CNH5730.91May23101252@calvin.tamu.edu> cnh5730@calvin.tamu.edu (Charles Herrick) writes: >Am I alone in thinking that >Izumi's post should be in the NeXTFAQ. >-- It is much too long to be included in the FAQ. However, I do agree that a pointer to the posting should be included in the FAQ. In addition, it may be a good idea to store the posting in the /pub/next/FAQ directory on sonata.cc.purdue.edu. I'll make the suggestion to the right people (in case this note goes unread).
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.