Wikis USB-Boot (en) 
Version 0.6.4 Initial Document This document is under construction!!! On the way to version V 1.0. Version 1.0 will be the first version starting the wiki. Up to then - you enter the grammar and orthography free zone -:)
[Edit]1 Howto Boot OS/2 - eCs from USB Mass Storage Devices ( MSD )
- English Version - Wiki
[Edit]1.1 Introduction
Cooperative Work based on the Wiki methode
Coauthors (In alphabetic order by first name):
Doug Bissett, Jan van Wijk, Juergen Ulbts, Martin Kiewitz,
Mike Luther, Oliver Rick, Peter Brown, Rainer D. Stroebel,
Steve Levin, William L. Hartzell
Initial author and moderator/editor: Rainer D. Stroebel
(mailto:RainerStroebelxyz@xyzt-online.de)
The Coauthors of the initial document has provided there input in newsgroups of comp.os.os2...
and DFSee support forums and eMails, not to this Wiki.
Thanks to Roland Schmalenberg and the Team OS/2 Köln/Bonn e.V for hosting
and technical support / administration of the Wiki
[Edit]1.2 History ( Logical View / not the version controll of the Wiki )
0.0 11.08.2006 Thread:
"Boot from USB PRM (Partitioned Removable Media ) failed
after loading OS2LVM.DMD error:
OS/2 is unable to operate your hard disk or diskette drive"
on comp.os.os2.bugs . Actually there are 2 threads,
one starting 11. Aug 2006 with 62 messages
and an follow up starting at xx jan, 2007 with 2 messages.
( Printout of the Thread about 60 pages!! )
0.4 xx.01.2006 eMail Dialog with Jan van Wijk,
Jan does a great job with evolutions in DFSee 8.11
0.5 25.01.2006 Start production of the Initial Document for the Wiki
copy the existing texts to the Wiki, structuring and editing
0.6 09.02.2007 Chapter: Problem reports / Found Defects in the Research
done documentation and research on problems
Thanks to Jan for the partitipation
moved topcis to sub wikis
0.6.1 15.02.2007 Add config.sys code: Case: Boot Large Floppy LVM
detecet Wiki Edit Problem with backslash in config.sys code
0.6.2 19.02.2007 new functions of DFSee V8-11 integrated to the Wiki
0.6.3 20.02.2007 add test result usage of the IBM BMGR,
Raw ideas for PRM LVM booting
hardware and software compatibility stuff
0.6.4 25.02.2007 Add picture and some text
[Edit]1.3 to do
a lot -:)
Currently the main focus it to document the positive result and the problem descriptions of the detected problems / bugs.
By authoring a comprehensive problem documentation we structure, verify and rethink the nature of the problem.
Good, exact, detailed, verified problem description are the half the solution :-)
Present the solution and problems as input to the readers works.
The introduction chapters currently are rudimentary. Here is more time and effort reQuired.
The main focus is to produce solutions. If we have solutions, we can go to the next step to present the solutions for early adapter. The Feedback improves the solution and the presentation of it.
[Edit]1.4 Terminology
Large Floppy ( BigFloppy , USBZip, Superfloppy )
USB Sticks,USB Key, USB Flash Drive, USB Hard Disk, external HHD s etc.
PRM Partitioned Removable Media
USBMSD USB Mass Storage Device
USB Universal Serial Bus
[Edit]2 BIOS Requirements
well, you need a
- Computer with USB BIOS Boot support
This is the BIOS configuration screen of the ThinkPad T23
Bild: USB-Boot-BIOS-Configuration-USB-Support-enable
- An USB MSD device with USB boot support
A hight number of USB sticks does not have this.
See USB Sticks test article in the ref of the Wiki
The CF Card is clearly specified.
So the safest way to boot from USBMSD ( to prevent hardware incompatibility problems )is to use CF Cards and a one slot USB CF Card Reader.
[Edit]2.1 USB BIOS Boot Support compatibility
I have done some research on this subject and found
a kind of compatibility list on the net
Forum: USB Booting - Topic: USB Boot Compatibility List 
(http://damnsmalllinux.org/cgi-bin/forums/ikonboard.cgi?act=Print;f=17;t=2925)
To collect compatibility information about Notebook / Motherboard and there BIOS release pleas
enter your test result to the SubWiki
[Edit]2.1.1 Collecting Ccompatibility Information about the hardware BIOS USB Boot Support via SubWiki
Please see SubWiki: USB BIOS Boot support Compatibility List
[Edit]2.2 USB MSD USB Boot Support Compatibility
Son of the USB 2.0 Hi-speed Flash drive roundup - April 13, 2005 By Matt Woodward (http://arstechnica.com/reviews/hardware/flash2005.ars)
==> Conclusio: Not all USB Stick are bootable
[Edit]2.2.1 Collecting compatibility information about the hardware USB MSD Boot Support via SubWiki
Please see SubWiki: Collecting Information about USB Mass Storage Device Boot Support Compatibility
[Edit]3 Hardware Requirement
Computer with USB port and USB boot BIOS support USBMSD with USB Boot Support
[Edit]4 Software Requirements
OS/2 or eCS with the latest USB version of the USB drivers
[Edit]4.1 Check the buildlevel of the key components of your system
Copy and paste the text from the SubWiki into a new File and save as "bld-dis.cmd" and run from boot drive
bld-dis.cmd > bld-dis.txt
Please see SubWiki: Command File to display the build level of the key components
The check the output of the command in file bld-dis.txt. Does your system use the current drivers?
These are the current buildlevel ( state: 2007-02-22 ) of the key components
os2krnl 14.103 or better IBM1FLPY.ADD 10.85 IBM2FLPY.ADD 10.57 IBM1S506.ADD 10.161 IBMIDECD.FLT 10.134 IBMIDECD.FLT 10.134 DANIS506.ADD 1.7.10 --- New 2007-02-22 !! DANIATAP.FLT 0.3.19 USBUHCD.SYS 10.162 USBOHCD.SYS 10.162 USBEHCD.SYS 10.162 USBD.SYS 10.162 USBHID.SYS 10.162 USBMSD.ADD 10.162 OS2DASD.DMD 14.104 OS2LVM.DMD 14.105
[Edit]5 Hard- and Software of the initial test environment
[Edit]5.1 Hardware test environment
IBM ThinkPad T23
UltraBay 2nd HDD Adapter
CF-to-IDE Adapter
USB CF Card Reader One Slot (USB 1,1 ) well the T23 does have only USB 1.1 ports
CF Cards 64 MB , 126 MB, 1 GB
The stuff with the CF-to-IDE Adapter in the UltraBay is test environment!
1. You see more info about your MSD Hardware by using DANIS506 and DiskINFO.
2. You can verify the OS/2 Configuration.
Does it boot via CF-to-IDE adapter and boot manager.
okay, no error
lets do the next step and test it with booting
via USB Card Reader,
USB BIOS support of the computer and
USBMSB I13 support.
Bild: USB-Boot-CF-64-to-IDE.png
Bild: USB-Boot-CF-128-to-IDE.jpg
Bild: USB-Boot-USB-Card-Reader-and-64MB-CF-Card.jpg
Bild: USB-Boot-CF-1-GB-to-IDE-A-DATA
Bild: USB-Boot-1-GB-to-IDE-DANE-ELEC
[Edit]5.2 Software test environment
OS/2 MCP2 with current Fixpak and driver level DFSEE version 8.11 or better DANIS506 package R 1.7.10 with Diskinfo UBS Resource Manager
[Edit]5.3 Basic step to create a testsuite
1. create a maintence partition on my primary HDD with BootAble 4.3
minimum features: only boot to cmd prompt, no wps support
USB Support basic and USBMSD.ADD
System is on Boot Manager Menu
Test the system (drive letter Y:)
2. take a CF Card and create a partition on the medium
How to do it:
data structure of the MSD: Large Floppy or PRM
For the case Large Floppy LVM System see at the step by step instructions in the paragraph
See Wiki Warum erkennt / arbeitet OS/2-eCS nicht mit meinem USB-Speichermedium? (http://p2066.typo3server.info/wiki-usb-tricks-de.html)
This is the German version of the Wiki.
The English version will follow in the next weeks with the VOICE article
3. There is no drive letter C:, D:, E: on my fixed HDD
The PRM partition has a drive letter of C: in my configuration
The Large Floppy have no assigned drive letter by LVM, no DLAT data structure !
4. Prepare the drive for boot
PRM: Sysinstx C:
Large Floppy: DFSee Version 8.11 or higher
5. xcopy y:*.* c:*.* /H /O /T /S /E /R /V
y: is the drive letter of the mini maintenance system
6. modify the config.sys
7. boot from USB MSD
7.1 Activate USB BIOS support
7.2 change the startup / boot sequence in BIOS
The PRM / Large Floppy is an hard drive for the BIOS
Set the primary hdd to the T23 inactive in boot menu - not in the boot sequence
Bild: USB-Boot-BIOS-Startup-Sequence
[Edit]6 Booting from USB MSD Mass Storage Devices
[Edit]6.1 Booting from USB Diskette
modifying the Service diskettes
Config.sys modifications:
1. rem Floppy
2. set CopyFromFloppy=1
3. Add USB Device drivers
4. special sequence for booting
USBDB.sys must be the first USB statement in config.sys
5. Require options USBDB statement
5.1 /I13 in USBDB.SYS
5.2 no parm /REQ for the driver ....
The set CopyFromFloppy=1
Environment variable must be used for special boot logic in the usb boot process
Without the the SET COPYFROMFLOPPY=1
==> MSG: "OS2 cannot access ..." occurs
Dirty hack?
[Edit]6.1.1.1 Config.sys for boot from Diskette LVM System
config.sys booting to command prompt ( with only a little cleanup, just from the test bench -:)
Please see SubWiki: Detail Listing config.sys
set bootdrive to ubsfloppy with drive letter a: ??????
Who is handling the drive letter a: and B: not DASD / LVM ??
/usage does not work in USB Boot process ???
Drive letters with two legacy floppy drive and 2 USB Floppy
how does this Hardware configuration work ??
Usage of drive letters? only a and b available for floppy devices?
====> Only tow floppy per system allowed?
I do see no use of this configuration, but it should work in theory. I have not seen any documented restrictions!
[Edit]6.2 Booting from USB CD-ROM
[Edit]6.3 Booting from Large Floppy
[Edit]6.3.1 non LVM Systems
[Edit]6.3.2 LVM Systems
The USB Mass Storage device can be formatted as Large Floppy or as PRM ( Partitioned Removable Media ).
This is the case with formated as Large Floppy and a system with LVM support
Restriction: It implies FAT16 and Size of MSD less 2 GB.
The basics of the detailed step by step instructions in the following paragraphs are:
1. Wipe the bootsector for a clean, new initialization
2. Write a special boot record to the media
3. Format the media as FAT16 Large Floppy
4. Xcopy of the mini OS/2 system via xcopy /h /o /t /s /e /r /v to the prepared Large Floppy
Now your USB MSD is ready for the test!
Next steps:
1. enable BIOS USB support
2. modify BIOS startup sequence
Now your system is ready for the test, are you ready? :-)
[Edit]6.3.2.1 Prepare USB MSD as Large Floppy for boot
1. Are you sure you can wipe your USB Mass Storage Device?
2. use DFSee Version 8.11 or higher
3. Look at the initial output of DFSee
Do you have the correct USB MSD to wipe?
4. Mode Fdisk
main menu Mode=Fdisk
sub menu MBR area operations
sub menu Wipe Start of disk to Zero
sel menu select line with your USB MSD
conf box Confirmation request
Are you sure the correct Disk to wipe? Check again !!?
conf box It is strongly advised to REBOOT the system now to allow it to determine
the correct disk geometry and size. This may be required to 'see' the
full capacity of the disk.
OK
5. Exit DFSee, shutdown system, reboot
6. Start DFSee again
7. look at the generated list output to check last operation
Check: 1. L-Geo and size of your USB MSD
2. No boot Record !
3. FreeSpace Pri/Log for your USB MSD
8. main menu File
sub menu Open object to work with
sub menu Disk
sel menu select line with your USB MSD
Be aware: DFSee will have selected Mode=FDISK here
because the disk is empty (wiped).
9. main menu Actions
sub menu Format with FAT filesystem
sel menu Current, OS2LDR.SEK bootable
Be aware: DFSee switches from Mode=FDISK to Mode=FAT
just before the confirmation box is displayed
conf box Confirmation request
Are you sure the correct Disk to format ? Check again !!?
YES
10. generate list output to check last operation
command line: map -M -m
F5 (part -r )
===> --r C: Large Floppy Format! FAT OS2LDR.s LargeFlopD2 xx MB for your USB MSD
Drive letter should be C:, if not, your configuration is not fit to boot from USB Large Floppy !!
see paragraph "Restriction: no Drive Letter C: should be used by the LVM Volumes" !!!
11. exit DFSee
Thanks to Veit (http://kannegieser.net/veit/index_e.htm) ( OS2LDR.sec ), to Jan (http://www.dfsee.com) ( new functions in DSFee 8.11 ) for the excellent jobs and
to Jürgen (http://www.juergen-ulbts.de/index.de.html) for the tip to have a look at MEMDISK!
[Edit]6.3.2.2 Copy your Mini OS/2 - eCS System from Maintenance Partition to prepared USB MSD
XCOPY x:*.* C:*.* /H /O /T /S /E /R /V
[Edit]6.3.2.3 Config.sys for boot from Large Floppy LVM System
config.sys booting to command prompt ( with only a little cleanup, just from the test bench -:)
Please see SubWiki: Detail Listing config.sys
[Edit]6.3.2.4 Restriction: no Drive Letter C: should be used by the LVM Volumes
The following system behaviour / logic is the reason for the restriction:
- The system assigns the drive letter C: to the Large Floppy in the first stage of the boot process.
- C: is the boot drive letter for LVM and the boot process after switching from real to protected mode.
- LVM detects a drive letter conflict, same drive letter on the "fixed" volume and on the "removable" volume
- The removable volume with drive letter C: does not have priority higher than the fixed volume with drive letter C:
- LVM resolves the double assignment of drive letter C:
- LVM assign the next free drive letter to the Large Floppy Device. e.g. drive letter D:
- The boot process switch from real mode to protected mode and continue the boot process with device with boot letter C:
If the fixed disk volume C: contains a valid OS/2 boot system,
the boot process continue with the config.sys from the fixed volume C:
else the boot process failed with message ?????. - If the boot process is successful ( sort of fake success )
the Large Floppy Drive can be accessed at command prompt with the new assigned drive letter.
- First command for the Large Floppy Drive has to be a dir or a chkdsk d: /F command
[Edit]6.3.2.5 Idea for further development - enhancement
- How to give the drive letter C: preference to a drive letter C: on the fixed disks of the configuration?
This is a most desirable feature. It dismissed the current restriction - no LVM drive letter C: on the fixed disks!
- Can we choose / assign a different / other drive letter to the Large Floppy Device to the default assignment of C:
This is a nice to have feature.
Solution: Filter Driver ?
[Edit]6.4 Booting from PRM
[Edit]6.4.1 non LVM Systems
The problem is to pass the boot drive letter during the boot process from the Partitioned Removable Media.
Boot Manager does not support PRM.
Howto supply a boot drive letter by booting from PRM.
Well, Danidasd.dmd does have an option for the boot drive.
There are some restrictions of danidasd:
1. Danidasd does not support the LVM info on the HDD.
2. The drive letter for the PRM is assigned by the "old" drive letter assignment method:
first assign a drive letter to all the "fixed" partitions (drives) and than to the "removable" partitions (drive)
the drive letter assigned to the PRM drive is depended from the layout of the HDD of the system to boot
The following system / config.sys on CF Card boots from USB card reader on my T23 system
It is on a FAT file system to keep it simple :-)
Please see SubWiki: Detail Listing config.sys
The version with the DANIDASD boot to the command prompt!!!!
Proof of Concpet !!!!!!!!!
[Edit]6.4.2 LVM Systems
In the thread on comp...bugs Mike reported success. He cloned a system ( a system with volume C without boot manager ) to an USB MSD external disk. This cloned system does boot from USB.
This message has been a great motivation to go on with the project. On the other hand I have not been is able to reproduce the reported boot.
Finally I had success. The system boots from the USB drive at the first stage of the USB drive. When switching from real mode to protected mode during the startup, the system does not only switch the mode, it does switch the boot device too! It switches from the cloned USB system to the source system on the fixes hard drive. Both systems are similar / equal, so the switch was not detected during the test.
The case has been detailed documented in the following SubWiki
Please see SubWiki: Detail Case Boot from PRM LVM System Case Fake Success
This case show the feasibility to boot from USB PRM. To understand the nature of the problem it does help a lot.
Two problems has been identified:
1. Tell the system the boot drive letter. For systems without BMGR, if assumes letter c for the primary boot partition. For systems with BMGR, the BMGR assigns a drive letter to each OS/2 boot system on the boot menu. For LVM systems the DLAT info on every bootable partition is evaluated. For non LMV system the drive letter are assign by chronological order of the partition starting with drive letter c.
2. pass the attribute boot drive with the boot drive letter to the LVM / DASD logic.
raw ideas ( as of 2007-02-20 Rainer ):
1. USNMSD.ADD new pram. Handle_First_Removable_as_Fixed_Device
==> Source Code of USBMSD.ADD needed
2. Special patched version of USBMSD.ADD ?
3. OS2DASD.DMD New Parm: Handle_First_Removable_as_Fixed_Device
==> Source Code of USBMSD.ADD needed
4. Filter driver to change type of first removable device to fixed disk
How to pass the boot drive letter of an USB MSD boot partition to the system?
Solution: Use ( Alternate ) Boot Managers
1. IBM Boot Manager
2. AiR-BOOT
3. VPART
4. XFDISK
5. GRUB
IBM Boot Manager
Does not install on PRM by LVM or LVM GUI
Workaround: use DFSee to install primary partition with boot manager on the PRM
Test results:
Boot Manager is loaded by the I13 access from PRM. Now the program logic of the BMGR is processed. Look for an other boot manager partition on the hdds of the system. Found one on the first internal hdd. This one get priority. Look for bootable partitions on the hdd (drive 0 ) to build the list of the boot menu. Look on the second drive ( drive 1 ) for bootable partition. Here the logic fail - It does not look at the PRM, the PRM does not have the BIOS type hdd, if look for a second internal hdd, does not find on and display error Message "Drive 1 not ready, system halted"
Internal boot manager program logic is derived knowledge from comp.os.os2.setup.storage Thread:
" "Drive 2 not ready" error - Warp4 - Dell XPS P200s - Boot Manager" (http://groups.google.com/group/comp.os.os2.setup.storage/browse_frm/thread/c889979f273ec13c/42b16149e501cce2?lnk=st&q=os2+boot+manager+drive+not+ready&rnum=2&hl=de#42b16149e501cce2)
This sounds like Boot Manager getting confused by the Bootable
CD support on this machine..
BM asks bios for the drives 80-97, looking for
disk devices, then ready devices..
Apparently the bios answers that the CD is disk and
ready, and then we try to read it and get the not ready error...
Sam Detweiler
IBM OS/2 Device Driver development
Conclusion: Do we have a chance to let the BIOS handle the PRM USB boot device like a HDD?
Question to the experts!!
Bootmanager AiR-BOOT
The current version is 1.5. The OS/2 installation program AirBoot2.exe is designed to load the manager into the first tack of your primary hard disk, not to the first track of an PRM.
Workaround: Prepare the CF Card with partition loaded with the mini OS/2 test systems and the an directory with the AiR-BOOT program package. Insert the CF card into an IBM Thin Client 8373-S20 and execute the installation program Airboot2 and configure AiR-BOOT. Do test boot on the Thin Client. Shutdown and move the CF Card to the test computer.
AiRBOOT require sector 2 to 60 of the first track of the boot device ( AiRBOOT documentation: developer.txt ).
AiR-BOOT consists of several parts:
- AiR-BOOT MBR Code (sector 1)
- AiR-BOOT Code (starting at sector 2)
- AiR-BOOT configuration (sector 55-59)
- AiR-BOOT MBR backup (sector 60)
Conclusion: MSD devices with tack GEO less than 63 sectors could not be used. CF Card up to 256 MB are of no use. We have to check the GEO before usage.
Next problem: DFSee does not show P-GEO values for PRM, just value zero. This problem is investigated. ==> "CF and GEO Problem"
Work around: Use the ThinkPad UltraBay 2nd HDD Adapter and an CF-to-IDE Adapter
Test results:
1. Feature: does not install on USB MSD
2. AirBoot2 - Installation process, no waring by disk with less than 63 sectors
3. IBM Thin Client 8364S20 and DANIS506.ADD R 1.7.9 does not work -- pip pip pip pip ...
needs special parms or this version is broken for Thin Client chip set
Workaround: Use IBM1S505.ADD
Status as of 2007-02-22: IBM Thin Client 8364S20 and DANIS506.ADD R 1.7.10 works
without any special prams !!
4. IBM Thin Client does not work with CF 1 GB 120x - Hang up in OS2DASD.DMD
Workaround: Use 1 GB CF Card with lower speed
5. AiR-BOOT works on ThinClient !!
6. Test via USB Card Reader and ThinkPad T23
6.1 First boot with AiR-BOOT: Warning Message BIOS changed, Virus?
6.2 Select System to boot, I/O activity on USB MSB, blink of cursor, no OS/2 blob
6.3 Modifies primary system boot sector of internal HDD!
This program feature / behaviour we do not need for our purpose!
A rescue task for DFSee :-)
6. e-mail to developer
Conclusion: The current version ( 1.5 ) of AiR-BOOT is not usable for the task
Bootmanager VPART
The current version is from 2001-11-08 . The OS/2 installation program VPARTOS2.exe is designed to load the manager into the first tack of your primary hard disk, not to the first track of an PRM.
Workaround: Prepare the CF Card with partition loaded with the mini OS/2 test systems and the an directory with the VPART program package. Insert the CF card into an IBM Thin Client 8373-S20 and execute the installation program VPARTOS2 and configure VPART. Do test boot on the Thin Client. Shutdown and move the CF Card to the test computer.
VAPRT require own code in boot record and sector 11 to 45 of the first track of the boot device ( VPRAT documentation: VPART.DEU ).
The install program VPARTOS2 asks very polite: "May i now write 1 sector in sector 1 and 35 in sectors 11 to 45 ?" :-)
Conclusion: MSD devices with tack GEO less than 63 sectors could not be used. CF Card up to 256 MB are of no use. We have to check the GEO before usage.
Next problem: DFSee does not show P-GEO values for PRM, just value zero. This problem is investigated. ==> "CF and GEO Problem"
Work around: Use the ThinkPad UltraBay 2nd HDD Adapter and an CF-to-IDE Adapter
Test results:
to be continued
No succes to report - jet :-)
===> *"OS/2 is unable to operate your hard disk or diskette drive"*
[Edit]7 Conclusio
1. The booting from USB Diskette LVM System - tested and works
2. The booting from USB CD-ROM - Currently not test, no USB CD-ROM aviabale
3. The booting from Large Floppy non LVM System - not tested, no software configuration aviabale
( should work no difference to LVM system )
4. The booting from Large Floppy LVM System - tested and works
5. The booting from USB PRM non LVM System - tested and works
( Prove of Concept based on DANIDASD.DMD for booting from USB MSD PRM ) !!!
6. The booting from USB PRM LVM System
under development / construction
[Edit]8 Problem reports / Found Defects in the Research
[Edit]8.1 CF and GEO Problem
The displayed GEO values by the IBM1S506.add, the DANIS506.add and GEO values in DFSee output ( here plus USBMSD.add ) differs.
Some values looks buggy!!
Please see SubWiki: Detailed Problem Description
[Edit]8.2 Large Floppy and SYSINSTX SYS01475
Obviously SYSINSTX does not do the job for the Large Floppy Format correctly!!
[Edit]8.2.1 Problem Descriptions
[Edit]8.2.2 Work around: Howto write a correct Boot Record for OS/2 to a Large Floppy
The subparagraphs "Problem Description" and "Work around: Hwoto ..." has been moved to SubWiki
The Header Lines with empty contents remain in the main Wiki to be shown in the main table of contents!!
Please see SubWiki: Detailed Problem Description and Work Around
[Edit]8.3 IBM Boot Manager and Wrong Drive Letter - Unable to boot a system from logical partition
The boot manager assigns a wrong drive letter to a bootable partition. Booting this partition via boot menu fails with error "OS/2 is unable to operate your hard disk or diskette drive"
Please see SubWiki: Detailed Problem Description
[Edit]8.4 Bootmanager AirBoot V1.5
[Edit]8.5 Bootmanager VPART
[Edit]9 References / Literaturhinweise / Linksammlung
USB Removables Care and Feeding FAQs by Lon Hooker, © June 2006
Druckansicht Startseite
Wikis USB-Boot (en) 
plugin.tt_news ERROR:No singlePid defined
No HTML template found
--> Did you include the static TypoScript template ('News settings') for tt_news?
